|Deletions are marked like this.||Additions are marked like this.|
|Line 2:||Line 2:|
Community Teams Process Docs
While we strongly believe that making Debian a good and welcoming place for collaboration is a responsibility of all members of our community, there's also a need for dedicated people to assist when things are not working so well. If you think you'd like to help, please contact us at email@example.com - we promise not to bite!
We will ask some questions about background (etc.) of new volunteers. Ideally, we'd like to see some existing experience of doing tasks like community support or mediation but that's not a hard and fast rule. We're also happy to work with less experienced people - everybody has to start somewhere!
One rule we must follow, however, is that CT members must already be Debian Developers. The job often includes private tasks and discussions that we can not reasonably share with non-DDs.
Assuming that we're all happy to proceed, we'll then invite new volunteers to work alongside the rest of the team for a short probation period. If all goes well, we should be happy to extend full access to a new member within a few weeks.
Adding / removing members
Here are the places we need to update when we need to add or remove a member:
Team wiki page: update membership in Teams/Community
- DSA: update mailing list aliases and Unix group membership (send an RT ticket to DSA to ask for that, inline signed)
salsa: update membership of the "community-team" salsa group: https://salsa.debian.org/community-team/-/group_members/ All delegated team members should be admins there, non-delegated folks should be added as "Maintainers".
- IRC - invite member to various channels as needed (some channels are private. so notlisted here)
- delegation - update membership periodically. Will need to discuss with the team and the DPL, of course.
- shared PGP key - share a copy of the private key and the passphrase. Cross-sign