[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #28643 [Internal Services/Service - github tpo]: New github team for manual and support
#28643: New github team for manual and support
--------------------------------------------------------+------------------
Reporter: teor | Owner: hiro
Type: task | Status: new
Priority: Medium | Milestone:
Component: Internal Services/Service - github tpo | Version:
Severity: Normal | Keywords:
Actual Points: | Parent ID:
Points: | Reviewer:
Sponsor: |
--------------------------------------------------------+------------------
emmapeel asked me to give her write access to the manual and support
repositories on https://github.com/torproject , so she can close pull
requests.
We give access to github/torproject using github teams.
People with write access can close pull requests, and push to branches.
Here's what I need to know:
Write access team:
Which repositories should the team have access to?
What should the team be called?
Who should be in the team?
What are their github usernames?
Do you need a team with admin access as well?
People with admin access can modify permissions, and delete or rename the
repository. (A few of us already have admin access to all repositories.)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28643>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs