TSC Agenda 2022-03-08

[jeremyong-az]

TSC Meeting Details

Date/time: 2022-03-08 @ 4PM UTC (8am Pacific) Location: Discord tac-tsc voice channel

Reply with a comment below to add items to the agenda

[hultonha]

Topic: Update on sig-simulation proposal Presenter: @greerdv Length of time: 5 minutes Information: (TBD - data being gathered) (attention of @SergeyAMZN, @moraaar, @amzn-jillich)

Topic: O3DE deprecation strategy Presenter: @greerdv Length of time: 5 minutes Information: RFCs to be drafted over the next several weeks, updated will be shared when they're posted.

[thefranke]

• Follow up on sig-simulation
• Follow up on code sharing of modified non-free SDKs
• Private channels on Discord

[greerdv]

Some data on the current admin load for sig-core and sig-content:

• a breakdown of github issues by sig looks like
  • 2855 : total
  • 1319 : sig/content
  • 475: sig/ui-ux
  • 371: sig/graphics-audio
  • 339: sig/core
  • 232: no sig label
  • 178: sig/build
  • 116: sig/platform
  • 89: sig/network
  • 71: sig/release
  • 30: sig/docs-community
  • 24: sig/testing
  • 16: sig/security
• so sig/content accounts for nearly half of all github issues (also about 1/3 of PRs), suggesting it is far too large
• feature/animation accounts for less than 10% of sig/content issues (109/1319)
• the biggest other labels in sig/content are editor (267 issues), scripting (190), prefabs (162), terrain (112), viewport (95), project-manager (73), asset-pipeline (54), lyshine (51)
• feature/physics (which currently includes destruction and cloth) accounts for nearly half of issues with label sig/core (154/338)
• sig/core is the 4th largest by issue count, and would still be comparatively large if the physics issues were split out
• the other issues in sig/core could use more granular labelling (I will bring that up in the sig-core triage meeting) but a rough categorization by me looks like
  • 30: asset pipeline
  • 23: project/gem configuration
  • 9: systems
  • 7: math
  • 5: settings registry
  • 5: feature/sdk
  • 4: serialization
  • 4: shape components
  • 3: AI
  • 3: AZStd
• The disjoint topics covered by sig-core are all mixed together on one channel in discord. For example, this is how many times some arbitrarily picked physics related terms appear in the sig-core text channel vs a few systems keywords:
  • physics (40), physx (17), blast (20), simulation (19), destruction (4), AI (4)
  • gem (149), asset (84), project (76), azcore (56), ebus (46), registry (42), azstd (33), bus (29), prefab (18)
• A similar mixture occurs in the sig-content text discord channel:
  • animation (113), actor (44), motion (20)
  • editor (203), asset (187), script (172), prefabs (149), project (93), pipeline (54), terrain (50)
• Quote from @moraaar - "In my case, I'm receiving many emails and PRs from sig-core that have nothing to do with physics/cloth/blast. Having sig-simulation would mean I'll be more efficient in detecting PRs, triaging bugs, giving support in discord and my time in meetings will be better use to discuss topics more relevant to my day-to-day work and that I have more expertise on."