feat(sig): add scalability group

[morey-tech]

Create the Scalability SIG based on the discussion in the community meeting on 2023-03-01 about docs: add scalability benchmarking proposal #12662.

Todo, pending approval of this PR:

• Create the argo-sig-scalability channel on CNCF Slack.
• Add the SIG Scalability meetings to the argoproj calendar.
• Create a Google Doc for the meetings and add the argoproj google account as the owner.
• Add GitHub App to Slack channel to post notifications for the type:scalability label.

[hblixt]

To create a SIG, you need a maintainer appointed secretary/coordinator, (https://github.com/argoproj/argoproj/blob/master/community/SIG-GOVERNANCE.md). That need to be figured out and the person appointed by the Argo maintainers before this PR can be merged and the SIG created
As there are also plans for an argo-labs repos, a project onboarding ticket is needed (https://github.com/argoproj/argoproj/blob/master/proposals/001-project-onboarding.md)
It might also be worth considering not intertwining the SIG and the repos too much e.g. the SIG has a broader charter around Argo scalability, whereas the argo-labs tools repos is focused on implementation but has an ownership/membership that's different than the SIG itself.

[morey-tech]

Thank you, @hblixt, for your review and guidance!

To create a SIG, you need a maintainer appointed secretary/coordinator, (https://github.com/argoproj/argoproj/blob/master/community/SIG-GOVERNANCE.md). That needs to be figured out, and the person appointed by the Argo maintainers before this PR can be merged and the SIG created

I'm happy to take on the coordinator role for the Scalability SIG. What is the appointment process, or where is best to reach out for an approval from the Maintainers? It would be good to add it to the SIG README, I could add a Role column in the Members table.

As there are also plans for an argo-labs repos, a project onboarding ticket is needed (https://github.com/argoproj/argoproj/blob/master/proposals/001-project-onboarding.md) It might also be worth considering not intertwining the SIG and the repos too much e.g. the SIG has a broader charter around Argo scalability, whereas the argo-labs tools repos is focused on implementation but has an ownership/membership that's different than the SIG itself.

Understood. The repo for the scalability benchmarking tooling will not be limited to the Scalability SIG and vice versa.

[hblixt]

Thank you, @hblixt, for your review and guidance!

I'm happy to take on the coordinator role for the Scalability SIG. What is the appointment process, or where is best to reach out for an approval from the Maintainers? It would be good to add it to the SIG README, I could add a Role column in the Members table.

I have added it as a topic to the Argo Maintainer meeting on 3/7. Would be good if you could be there @morey-tech

[morey-tech]

I have added it as a topic to the Argo Maintainer meeting on 3/7. Would be good if you could be there @morey-tech

Great, thanks! I'll be there.

[morey-tech]

Based on the conversation in the Argo Maintainers Meeting on 2023-03-07; to promote engagement from the broader community before proceeding with the formal approval, we will move forward with holding the SIG Scalability meetings, along with posting in the CNCF Slack channel.

In support of this, I'll arrange to create the meeting log document, Slack channel, and schedule the recurring meeting on the argoproj calendar.

[csantanapr]

@morey-tech

In support of this, I'll arrange to create the meeting log document, Slack channel, and schedule the recurring meeting on the argoproj calendar.

your a star ⭐

[vsethi]

Request for membership

[morey-tech]

The Scalability SIG was officially approved during the maintainer's meeting today. This PR is ready to be merged.

[hblixt]

Approved as per the maintainer meeting 5/2.
Looking forward to lots of valuable content from this SIG!