Creating a GitHub Team
Once logged into Syracuse University's instance, create a GitHub Team - Create Team
To enable easier collaboration and discovery in the platform consider names that include identification that is more specific to your area vs generalizing. For example, "infrastructure" may encompass multiple areas. Use "web hosting infrastructure" or "{dept}-infrastructure". Where possible users should name their Team based on the following naming convention: "ITS-(Department/Team Name/Acronym)-(Role if required)". e.g. "ITS-CIS"
"Visible" teams are recommended so that collaboration can be made easier and requests to join can be made.
Nested Teams or building Teams play a crucial role in managing GitHub projects and repositories. They offer the ability to regulate user access and permissions for collaborative efforts.
Consider naming your team according to the following convention:
Department-Team(-SubTeam if needed)-Role
Ensure that Team/SubTeam names are descriptive, and make the team "Visible" to facilitate discovery and collaboration for others.
Publicize your Team's GitHub URL within your department to encourage members to join the GitHub Team.
Nesting Teams (Placing a team in a Team)
It's generally not recommended to use nested teams unless necessary.
However, establishing a hierarchy of parent/child teams in certain situations can have some provide advantages for large teams in specific situations.
Child teams inherit the parent's access permissions of their parent, simplifying permissions permission management for large larger groups.
Members of child teams also receive notifications when the parent team is @mentioned, simplifying streamlining communication with across multiple groups of people. Generally, we do not recommend using nested teams unless required since the relationship of a child team to its parent may result in users having access to a repository that you did not intend. If there is a new group of people working on a repository, create another Team.
In some situations, you may want to create separate Teams for differencing level of access to the Team's repositories. For example, it may be required to create a Team named "ITS-IAM-Admins" to provide a smaller scope of user access to the Admin role of the Team's repositories instead of the whole "ITS-IAM" team.
Setup Team Maintainers so that requests to join the Team can be approved - Setup Maintainers
There should be at least two group maintainers so .
If the current nested relationship extends access beyond the intended scope of the existing team, it's best to create another Team to represent the new scope of people.
Team Maintainers
Establish Team Maintainers to approve requests to join the Team.
Ensure there are at least two group maintainers. This redundancy ensures that if one person is unavailable, another Team member can perform fulfill the administrative duties of Team maintenance.Publicize your Team's GitHub URL so that other members of your department can join the GitHub Team.
Join a GitHub Team
GitHub repository and project permissions are best managed with GitHub Teams. if you have been given a Team name to join follow these steps.
Navigate to the Syracuse University Organization.
Select the "Teams" tab from the row of available options near the top of the page.
Search for the Team you would like to be a member of.
Select the Team, and click the "Request to join" button to send an access request to the Team Maintainers.
A Team Maintainer will now be able to review your request to join and will approve or deny based on their discretion.