TSC montly All-SIG meeting and roadmap board review (2/28/2023) about tsc HOT 11 CLOSED

sig-simulation - https://github.com/orgs/o3de/projects/23

It's a tiny bit out of date but a new roadmap task to track articulation and robotic arm support will be created soon (see this RFC for details o3de/sig-simulation#60

Tagging @lgleim and @epsilon-delta for visibility

New roadmap initiative - o3de/o3de#14851

RFCs in-progress related to articulations: o3de/sig-simulation#60, o3de/sig-simulation#57

from tsc.

SIG/Network: https://github.com/orgs/o3de/projects/22/views/1

• Mostly working on new O3DE multiplayer sample, which is driving a lot of underlying changes in O3DE (Audio & Vfx fixes, fixed profile builds with PAKs).
• (Not O3DE but of note) AWS made an open source O3DE multiplayer scaler project (supports for launching 500 clients against an O3DE multiplayer server. New sample team is using this to drive networking performance changes for new multiplayer sample
• Discussing planning for feature work around improving the experience of making redistributable builds
• SIG held new elections, current Chair/Co-chair were relected (lmbr-pip, kberg)

SIG/Security - https://github.com/orgs/o3de/projects/45

• No planned features, SIG is mostly administrative to ensure security issues are addressed in a timely manner.
• SIG is planning for new elections

from tsc.

(on behalf of ) SIG/Core

• Starting the long road to deprecate AZ_TracePrintf: o3de/o3de#14838

from tsc.

SIG Docs & Community: https://github.com/orgs/o3de/projects/15

• Completed backlog refinement. Closed out 45 issues in o3de.org repo
• SIG D&C planning for new elections
• SIG D&C meeting moved to 1st Tuesday of the month. Triage remains weekly on Tuesdays.
• Working with sig-release to make Roadmaps discoverable from the documentation, Contributing Guide. (Making the roadmap discoverable in the main website is part of the website development plan, which is owned by Marketing.)

from tsc.

SIG-Release
@tonybalandiuk is unable to make it to this meeting, and the co-chair @vincent6767 may also miss it.

What we did last month

1. There are 3 SIGs left to create the roadmap according to the RFC.
2. Started discussion about what the repositories included in the process. This started due to an O3DE-extras discussion.
3. Started a discussion to increase community awareness of the roadmap by sharing those in the docs and main websites: o3de/sig-docs-community#102. Collaborating with SIG-docs-community
4. Decided on the next release 23.05 on May 3rd, 2023: o3de/sig-release#133 . Stabilization branch phase will start on March 15th, 2023 10 AM PST. If you have any concerns with the schedule please comment under the issue ASAP.

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

1. Mar 15: Start the 23.05 stabilization process: o3de/sig-release#133
2. Work with with docs-community, TSC, and marketing to surface the O3DE roadmaps on the O3DE websites: o3de/sig-release#137
3. Decide criteria for repositories to be included in a release. o3de/sig-release#129
4. Decide whether to include o3des-extras as part of the O3DE release or not.
5. Complete documentation of the O3DE release process: o3de/sig-release#134

from tsc.

SIG-Release Latest Updates on the Roadmap effort.

1. All SIGs now have a roadmap, except for SIG Security and Operations as they don't have any planned roadmap yet. Thanks, everyone for helping with this effort! https://github.com/orgs/o3de/projects?query=is%3Aopen+SIG .

CC: @tonybalandiuk

from tsc.

This is the sig-graphics-audio roadmap

I'd like to discuss the following items:

• o3de/o3de#12009 on Windows update
• sig-uiux: Is there a plan to eventually move to QT6?
• Getting calendar entries for wg-mobile
• Adding non-developers to the org to maintain project boards

from tsc.

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

• SIG-Core is currently attempting to gather nominations for a Chair/Co-Chair: o3de/sig-core#51
• Research into improving developer iteration speed of using O3DE (Split AzCore, AzFramework and AzToolsFramework into smaller libraries, based on usable roles, Convert AzCore, AzFramework and AzToolsFramework into shared libraries(.dlls, .so, .dylib) in non-monolithic TARGETS, Reduce the number of core gems that reside in the O3DE repo, Form solutions to reduce build times in high impact areas such SerializeContext, BehaviorContext, TypeInfo, EBus, Component ...)

from tsc.

SIG-Build roadmap https://github.com/orgs/o3de/projects/39 items:

• o3de/sig-build#79 RFC on methods to reduce cost for AR
• o3de/o3de#14733 on updates to min spec for Windows

from tsc.

I wanted to raise awareness that SIG-Content plans to

1. enable the canonical o3de remote repository in an empty state (no content) for the upcoming release, baring any unforeseen legal, security or technical issues that arise.
2. once the official approval process has been finalized, approved content will become available via the canonical o3de remote repository and in the Project Manager (o3de.exe)

SIG Content roadmap: https://github.com/orgs/o3de/projects/37 items:

• o3de/sig-content#110

from tsc.

SIG-Testing roadmap https://github.com/orgs/o3de/projects/35 currently has three prominent items:

• o3de/sig-testing#63
• o3de/sig-testing#62
  • o3de/sig-testing#64 (dependent on metrics)

Feedback would be appreciated on the open RFC for o3de/sig-testing#66

from tsc.