Add scottrigby and CrisNevares as admins of cncf/communitygroups

[scottrigby]

@hspease99 met with myself and @CrisNevares about helping with admin support and other automation tasks for the cncf/communitygroups repo. This issue is for transparency.

There may be others who could also help, and it may make sense at that point to create a GitHub team (eg @cncf/community-admin-support), but to enable initial support the easiest step we discussed would be adding us both as collaborators on this repo. The Admin role would allow us to help with repo settings (see Repository roles for organizations for list of permissions per role).

[hspease99]

Hi @scottrigby! 👋 Thank you for creating this issue. Apologies, this fell off my radar a bit since our last meeting. I still need to sync internally with the team on how best to structure this/if there are any internal procedures I need to consider. I will sync with the team and circle back here. In the meantime, can you and @CrisNevares drop the list of automations we discussed here?

[scottrigby]

I still need to sync internally with the team on how best to structure this/if there are any internal procedures I need to consider.

sounds good 👍

Note that there are additional community members who have offered to help with this as well, so perhaps we could discuss roles and a way to enable others to contribute to this too.

In the meantime, can you and @CrisNevares drop the list of automations we discussed here?

Yes, we mainly discussed some examples of changes that would reduce your burden doing manual tasks for all of the community groups by structuring this repo in ways that would allow organizers of those community groups to do themselves. The initial step we talked about was having a few trusted people who already administer CNCF projects, working groups, etc to meet with you regularly to try out ideas that could help you, and iterate on improvements in this repo as needed.

Some of the automations and repo changes we discussed:

1. keeping community group information somewhere in Git. this repo seemed the natural place, since issues are being used for this already
2. potentially GitHub actions to allow this info to sync a canonical list with other files as needed (eg, keeping a repo-wide CODEOWNERS file in sync with OWNERS files in a folder per community group)
3. enabling community organizers to make PR-based requests instead of issues that require manual work by Helena to manage in a separate DB (relates to # 1 above)
4. GitHub actions in this repo to help with other repetitive tasks that Helena has to do
5. allow community groups to centralize documents important for running their group and for the community in those locales to get involved

Some strategies discussed:

• integrate with OCG (https://github.com/cncf/open-community-groups) when stronger APIs and other mechanics would be useful, rather than complex one-off actions
• a CODEOWNERS file to allow organizers of each group to manage their group's directory

I know there were other ideas too but hope this helps as a start.

[scottrigby]

A contributor ladder for the cncf/communitygroups repo was added last week, so cross-referencing this: https://github.com/cncf/communitygroups/blob/main/contributor_ladder.md (thanks @AudMonte01)