Joint SIG:TSC Agenda 2022/05/24

[jeremyong-az]

Joint SIG:TSC Meeting Details

Date/time: 2022-05-24 @ 8am Pacific (Timezone Converter)
Location: Discord tac-tsc voice channel

[forhalle]

I'd like to discuss the following item at the upcoming TSC meeting:

We are looking for a volunteer to lead Cross-SIG Triage (see this post, which has been amplified here). If we are unable to identify a new owner by the end of the month, Tuesday 5/31, we will stop executing the Cross-SIG Triage process. The impact is SIGs will need to adjust their triage process / filters to review all GHI issues and PRs not assigned to a SIG for potential addition to their backlogs - we will no longer assign incoming GHI issues and PRs to the appropriate SIG.

Update 5/24: We may have found an Amazon volunteer to lead cross-SIG triage once weekly. This may work for the interim, but is not scalable. We suggest the TSC consider implementing a rotation for this activity amongst SIG Leads. If the process is instead cancelled, then we suggest TSC consider implementing automation to email any issues not picked up by a SIG in a reasonable amount of time to the sig leads for final consideration before auto closing.

Notes from 5/24 TSC:

• It was concluded to not pursue implementing a SIG rotation for cross-SIG triage due the difficulty in aligning schedules across multiple entities.
• The TSC was comfortable, however, with leaving this triage to the SIGs themselves (as this is a common pattern for open source projects).
• If we do not find a volunteer to lead this effort, @forhalle will communicate out the impact to SIGs (they need to triage issues with no sig/ labels)
• Regardless, @forhalle will add an item for sig/operations to create a bot to auto-close stale issues (perhaps post emailing a list to sig leads for final consideration), and will indicate critical/blocker issues should be escalated on a more frequent cadence that other issues. <= See Proposed RFC Suggestion: Bot for escalating and auto-closing issues w/ no sig/ label sig-operations#38

[jeremyong-az]

Topic: Role of the development branch, AR stability, runtime, contributor friction

[allisaurus]

At the next TSC I'd like to discuss guidance around moving code (i.e., the AWS Gems) out of the main o3de/o3de repository. Specifically, I have questions like:

• do we have, or can we come up with, a clear definition of what should be in the main O3DE repo?
• what is/should be the process for changing ownership of code currently within O3DE?
• what is/should be the process for changing ownership of docs in o3de.org?
• there is no (as far as I know) agreed upon way or place to promote discovery of gems external to the o3de/o3de repo. Where and how could we do this?

NOTE: It looks like the agenda for this day might be pretty full already, I'm amenable punting to the following occurrence if time doesn't allow on 5/24.

[aFinchy]

Hi All,

Wanted to propose these topics to be discussed.

• Wanted to bring up the process for the chairs who want to no longer be chairs.
• Those chairs who run more than one SIG and how it can become issues
• Frequency for SIG chair nominations.
• Wanted to bring up the option for making a section where SIGs can post tools that could be a easy task for anyone looking to contribute as a getting started on the engine to contribute. (That way its not like "oh hey, contribute to this month long tool")