Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

📝 Document onboarding member to the team #48

Open
jefftriplett opened this issue Apr 17, 2024 · 1 comment
Open

📝 Document onboarding member to the team #48

jefftriplett opened this issue Apr 17, 2024 · 1 comment

Comments

@jefftriplett
Copy link
Member

@jefftriplett jefftriplett changed the title Document onboarding member to the team 📝 Document onboarding member to the team Apr 17, 2024
@thibaudcolas
Copy link
Member

Here are changes I would recommend, for others to review, with the goal to simplify onboarding and offboarding:

  • As we discussed, add a chair@ email alias to facilitate CoC reports (Reporting guide information is out of date #50)
  • The Chair, Co-Chair, Board Liaison should get the "Maintainer" role on the CoC committee GitHub team, so they can self-manage members. I believe this would also allow adding to the Django GitHub org
  • The Chair, Co-Chair, Board Liaison should get the "Manager" role in Google Groups, also so they can manage membership.
  • The Google Docs / Drive access could be set to the group email, which I believe would automatically transfer to all members

I don’t know what roles the group members currently have, so most or all of the above likely requires the Operations team to set those Chair / Co-Chair / Board Liaison permissions once we did have a Chair / Co-Chair.

@elena elena pinned this issue Nov 17, 2024
@elena elena unpinned this issue Nov 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants