[INFRA-154] Update github organization member procedure to enable non-team member option Created: 15/Sep/17  Updated: 13/Feb/18  Resolved: 12/Feb/18

Status: Done
Project: Software Development Infrastructure
Component/s: web
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: shimono Assignee: shimono
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

github organization can have organization member without any team involved (need to be checked).
currently, we set all members to be in a team (for admin priv on relevant repos to team), but most of members do not need such priv for operation, but just need write access to repos.

add lines to management document(s).



 Comments   
Comment by shimono [ 14/Nov/17 ]

PR@github.

Comment by shimono [ 12/Feb/18 ]

merged. marked as done

Comment by naoyuki.tamura [ 13/Feb/18 ]

I didn't write any comments while I was being requested to do so and therefore I am obviously too late, but let me write a few lines mainly for my understandings

So far we "automatically" put all members at least in one of the teams. This means that all the members are given admin privileges although some of the privileges are not needed for ordinary use of repositories.
So you think it would be better not to give admin privileges to more members than needed, and to implement this arrangement, you proposed users to send specific requests to be team members if they want/need to, while they would allow not to belong to any teams.
Is this a correct understanding of what wants to be done in this ticket?

Below are the texts with some minor updates (as a suggestion):

PFS project uses Subaru-PFS organization at GitHub. To work on repositories in such manners as pushing codes and documents or reviewing PR, you need to be a member of team(s) that own and manage the repositories, or "outside collaborator" to the repositories of Subaru-PFS organization. For the institutes actively working on software development, one team (that is often private) is defined per group (any one of the following three: Instrument, data reduction, and survey) and is allowed to have admin privileges to repositories to be owned and managed by the team. If you plan to work for some repositories, you should send specific requests by e-mail to guthub at pfs.ipmu.jp to be a member of the team(s) or an outside collaborator to the repositories.

Generated at Sat Feb 10 16:49:57 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.