[RFC] Should we decommission the Core Triage meeting?

[peternied]

Is your feature request related to a problem? Please describe

Check the OpenSearch Meetup Group for the latest schedule and details for joining each meeting. Each component area has its own meetup series: Search, Storage, Cluster Manager, Indexing, and Core.

From TRIAGING.md

In the past two months the Core triage meeting has always triaged down to zero issues and attendance has flagged, from more than 10 participants down to an average of three. I would attribute this to the five standing triage meetings run for OpenSearch that provide additional time options and different domain experts to consult.

The core triage meeting was created when there was a large backlog of untriaged issues and there were no standing meetings, with todays posture the OpenSearch project seems in very good health and I'd recommend retiring this series at the end of this month.

Lets collect votes to end the core triage meeting

• 👍 End the core triage meeting series on July 31st
• 👎 Keep running the core triage meetings

Voting will close at the end of the 7/24 Triage meeting [2] when a decision will be reached.

Additional Details

• [1] https://www.meetup.com/opensearch/events/301175394/

[andrross]

I'm in favor of decommissioning the core meeting in favor of the domain-specific meetings. How do we ensure we get 100% coverage on new issues across the different meetings though? Currently each component only looks at a subset of labels and core was functioning as a catch-all.

[dblock]

I hear that the component triages do look at issues outside of their component, so the weekly catch-all triage is happy to be the catch all for all repos, including core, for the things that do fall through.

[peternied]

[Triage - attendees 1 2 3]
@peternied Thanks for creating this issue.

[peternied]

[Triage - attendees 1 2]
Based on votes, we are going to select End the core triage meeting series on July 31st - Thanks everyone for your input.