All-Sigs roadmap meeting for end of 30th of May 2023

[nick-l-o3de]

8AM Pacfic Time (US) in the TSC/TAC discord channel, will be the monthly "all sigs" status update and roadmap on 5/30/2023 (TUESDAY)

See the previous agenda for an example:
#74

Please attach links to the SIG roadmap (And anything to notify teams of in case of your absence, it will be read for you), in comments below. along with any agenda items.

[Naomi-Wash]

@lawsonamzn Can we update the date to 30 May which is Tuesday?

Suggested Agenda Items:

Master Roadmap

• Can we restart and build on this?
  • Changing/adding columns? (example: Goals, Possible Features of xx Release)

[vincent6767]

Will be late for 15 - 20 minutes to the call.

SIG Release roadmap: https://github.com/orgs/o3de/projects/29

What we did last month

1. Released 23.05 in collaboration with other SIGs and gathered release feedback from the team.

What we're going next month based on the roadmap: https://github.com/orgs/o3de/projects/29

1. Do the 23.05 release retrospective, and decide on the next item of improvement.
2. Together with TSC to decide whether we would want to mention the roadmap maintenance are one of the SIG responsibilities on the SIG charter. This is the issue that tracks this discussion: Add roadmap maintenance as SIG's responsibility on each SIG charter. sig-release#146
3. Start a discussion about the next release date.

Proposed Agenda

1. To discuss features grid maintenance effort and make sure everyone agrees that it's important to be maintained.
   1. Challenges
      1. The features grid is one of the release deliverables. Updating the grid generally involves two steps. First, SIG has to manually update each of the sections that it owns, along with other release deliverables. Second, the SIG Community-and-docs converts the grid's JSON file into a document format (I believe it is a markdown). You can see what it looks like on the docs page here.
      2. Few challenges faced in the past two releases
         1. SIG needs to spend time manually maintaining the grid in addition to its other responsibilities. It also requires two approvals, which makes it even slower.
         2. The Release manager needs to persistently remind SIGs to update the grid as the task is often buried by other higher-priority tasks.
         3. It takes time for SIG docs-and-community to convert the JSON into the markdown format.
      3. Questions to be discussed
         1. It takes effort to maintain the feature grid. However, the SIG release does not have visibility of how helpful the feature grid is to the community. Given that condition, SIG release would like to open a discussion with TSC and other SIGs to make sure the feature grid is still important to be maintained and everyone agrees that it is part of the O3DE release deliverable.
2. Decides the next steps for mentioning the roadmap maintenance responsibility in the SIG charter (or general guidelines).

[lemonade-dm]

SIG-Core Roadmap: https://github.com/orgs/o3de/projects/31

• Work on the replacement Archive System is underway with the initial Archive Gem being merged last month
• Updates to better support Remote Gem version continues as part of RFC Proposed RFC Feature Engine, Project and Gem Versions sig-core#44