Between the Samvera GitHub Organizations, users are structured into the following teams:
| Team | Description |
|---|---|
| admins | Users with administrative privileges for the Samvera Organization |
| contributors | Users with the privileges to manage releases for GitHub projects, as well as publish releases to RubyGems |
| emerita | Users who are no longer active within the Samvera Community, but who have contributed to community projects |
| maintenance | Current, active members of the Component Maintenance Interest Group |
| Team | Description |
|---|---|
| admins | Users with administrative privileges for the Samvera Labs Organization |
| contributors | Users with the privileges to manage releases for GitHub projects, as well as publish releases to RubyGems |
| maintenance | Current, active members of the Component Maintenance Interest Group |
| Team | Description |
|---|---|
| admins | Users with administrative privileges for the Samvera Deprecated Organization |
| contributors | Users with the privileges to manage releases for GitHub projects, as well as publish releases to RubyGems |
| maintenance | Current, active members of the Component Maintenance Interest Group |
GitHub Organizations distinguish between owners and moderators. Members of the admins Team possess both of these privileges.
By default, all other members of an Organization should belong to the contributors Team. As there are currently no requirement to be added as a member to any of the Samvera Organizations, there is no existing process for admitting new members. Additionally, members of the contributors Team possess the privileges to push new releases of Samvera Gems to RubyGems. Samvera Community members requiring these privileges can request them on the #dev Channel on the Samvera Slack.
While there is no formal process for auditing GitHub Organization membership, those members of Samvera Organizations who are no longer actively contributing to or in contact with the community should be contacted. Failing to receive any response, should these persons have contributed to any project in the past, they should be moved to the emerita Team. Otherwise, removing these persons from the contributors Team (along with their membership to the samvera and samvera-labs) is the best recommended practice.