samvera / maintenance

Organizing repository for the Core Components Maintenance Interest Group.
Apache License 2.0
0 stars 3 forks source link

Audit the structure of GitHub Teams for the samvera Organization #82

Closed jrgriffiniii closed 1 year ago

jrgriffiniii commented 2 years ago

The following Teams currently exist for samvera:

jrgriffiniii commented 2 years ago

My proposal would be that one please restructure these into the following:

Perhaps the following should also be available, however I am uncertain as to the status of these solutions:

hackartisan commented 2 years ago

It sounds like some clean up is definitely in order.

It would be helpful to define the use cases for the teams. Maybe we could reduce maintenance a lot here by eliminating most of them. Are they mostly so people have a group to tag for PR review? If so it may be that a message slack serves that purpose pretty well if not better. Is there another use for them?

jrgriffiniii commented 2 years ago
jrgriffiniii commented 2 years ago

The secret teams have now been deleted from the Samvera Organization.

jrgriffiniii commented 2 years ago

https://github.com/orgs/samvera/teams/hyku/teams seems to have been actively used, and hence, @jrgriffiniii will contact the members before requesting to delete this Team.

jrgriffiniii commented 2 years ago

Updating the admins team to have the description updated from:

Folks who have signed CLAs and requested admin access to one or more Hydra repositories. Ping a Hydra org admin (https://github.com/orgs/projecthydra/teams/admins, e.g., @mjgiarlo) if you'd like to join this team.

...to:

Folks who have requested admin access to one or more Samvera repositories. Ping a Samvera admin (https://github.com/orgs/samvera/teams/admins, e.g., @jrgriffiniii) if you'd like to join this team.

jrgriffiniii commented 2 years ago

Currently, the structure of the GitHub Teams now resembles the following:

jrgriffiniii commented 1 year ago

This should be resolved by what was undertaken in support for #83