TSC Agenda 2022-01-04 about tsc HOT 6 CLOSED

• Can we add a link to wherever the TSC meeting notes are archived to the repro please?

• SIG-Network has cross-SIG RFC (o3de/sig-network#32). Wanted to check about how we should approach cross-SIG RFC signoff. Do we get sign-off from all impacted SIGs? Do we need sign-off from TSC? Looking to ensure we meet expectations and we can be clear about future RFCs.

• SIG-Security would like to setup a security-reporting vulnerability process. Wanted to discuss how we approach this and what requirements the Linux Foundation have, as a LF hosted project. Reporting proposal discussion: o3de/sig-security#9.

  • This does not cover the mechanisms for who is on the report response team (need to discuss with TSC about approach), how we securely discuss issues or how triage/handling works. There would be a secondary proposal for report triage and handling.

• RFC archiving - SIGs currently archive RFCs in their own repros, should we be using the o3de/RFC repro as well? Discovery of accepted RFCs is currently hard (unsure if this has been discussed at the TSC prior due to notes discovery issue).

from tsc.

I'd like to discuss adding labels
o3de/o3de#6529

from tsc.

Generally meeting notes will be added as a comment to this agenda issue (as there's no need to explicitly version the meeting notes themselves or edit them post-facto). This lets us also have the notes inline with any discussion on the agenda itself. Note that some meetings do not have notes because the meetings themselves were not held due to not have quorum or some other reason (e.g. scheduling issues, etc.)

from tsc.

From our prior discussions, it would be good to talk about an update on the feature grid and maturity of each area by component.
This is necessary so that the community can focus its resources and not duplicate efforts.

from tsc.

Please note that date given for the TSC meeting above is incorrect. It should be Jan 4, not Jan 3.

from tsc.

Thanks, fixed (it's correct in the issue title)

from tsc.