The github docs are a bit unclear about the semantic difference between organisation member and outside collaborator. What is the distinction?
I run an github organisation for my school. I create repos and allocate them to students. Should the students be members of the org or outside collaborators?
An outside collaborator is a person who is not a member of your organization, but has access to one or more of your organization's repositories. You can choose the level of access to grant for each outside collaborator.
A user who has read-only access to a private repo should be marked as a collaborator, in my understanding. A user who has permissions to a repo but no commits in that repo with any of email addresses associated with their github account would be a collaborator but not a contributor.
Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once, with sophisticated security and administrative features.
Adding outside collaborators to a repositoryUnder your repository name, click Settings. In the left sidebar, click Collaborators & teams. Under "Collaborators", type the name of the person you'd like to give access to the repository, then click Add collaborator.
This particular GitHub Help Doc page may help clear it up. Outside collaborators only have access to repositories that their team membership allows. Outside collaborators cannot create teams or view all the organization's members and teams.
Outside collaborators and bot accounts will count toward your organization's total of paid seats if they are given access to a private repository.
Many people are confused by the real-world usage of outside collaborators. Here is the real-world use case.
Your company launches 2 projects, called PA and PB. They are maintained by 2 different "outside collaborators/teams" named TA (for PA), TB (for PB).
Organization members are able to see any projects created within the organization. There is no way to change this, at least for now.
Outside collaborator is used to restricting the visibility of packages within an organization. For instance, invite team TA to project PA, team TB to project PB, and NOT adding any of team TA or team TB as an organization member.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With