| layout | content |
|---|---|
| permalink | /faq |
The FAQ portion of this site aims to answer common questions posed by new Organization members.
{: style="text-align: center;"}
About Unipisa Organization Membership
About Repositories
About Teams
About Permission Levels
About Projects
{: style="text-align: center;"}
Have a question that isn’t answered here? Contact us !
{: style="text-align: center;"}
A: Membership to the Unipisa GitHub Organization is limited to current Università di Pisa faculty, staff and students, through invitation only. To register for membership, visit the Università di Pisa GitHub Page and navigate to the Join Organization section. Once there, enter your GitHub account username and unipi email address. A verification email will be sent to the supplied institutional email address. Once verified, an invitation to join the Unipisa Organization will be sent to the email address associated with your GitHub account.
A: You can view the profiles and public teams of other members. You can apply for your repository to be added to the Organization; refer to About Repositories. You can create Teams; refer to About Teams. You can create Organization Projects; refer to About Projects. You cannot create/transfer repositories from your account directly to the Organization. You cannot invite other users to the Organization. You cannot push to repositories that you do not have write access to.
A: Public Unipisa GitHub Organization members can only add a repository by emailing an application for their repository to the owners of the Unipisa Organization through the Add Repository section. If the application is approved, an owner from the Unipisa Organization will fork your repository into the organization. Since all permissions are wiped when the repository is forked, the owner will grant you admin privileges to the forked repository. If the application is denied, an owner for the Unipisa GitHub Organization will provide you with an explanation of why your repository was denied in an email response.
Q: Am I required to provide an open-source software license for the repository I would like to add to the Unipisa Organization?
A: See this Licensing section.
A: As a member, you can only delete a repository to which you have admin permissions to.
Q: As a Unipisa Organization member and the admin of a forked repository on the Organization, how can I manage permissions to the repository?
A: As an admin, you can manage permissions by creating new teams or adding existing teams to a repository. More information about GitHub Teams can be found here. An admin can also add individual collaborators to a repository with read, write, or admin privileges. Unlike Unipisa Organization teams, individual collaborators do not need to be members within the Unipisa Organization.
A: Teams are a way for organization members to manage permissions to repositories within the organization.
Please have a look at here and here for documentation about GitHub Teams and their usage.
A: Any Unipisa Organization member can create a team.
A: Only the team’s maintainers can edit the team’s settings.
A: Only the team’s maintainers can delete a team.
A: There are two different roles within a team, team members and team maintainers
A: A team member has access to each of the team’s repositories based on permission levels set by an admin of the repository. The admin of the repository can be, but does not have to be, a member or maintainer of the team.
A: You can become a team member by being manually added by a team maintainer or by going to the team page and requesting membership. A team maintainer would then approve or deny your request.
A: A team maintainer is a team member with elevated permissions around who is in the team and what repositories the team contributes to. A team maintainer can add an organization member to the team as well as remove a team member from the team. Team maintainers can promote other team members to team maintainers. A team maintainer can also add a repository to the team of which the maintainer has admin access to.
A: You can become a team maintainer by getting one of the current team maintainers to promote you. As expected, when you create your own team you become the team maintainer of your new team by default.
A: Yes, you can be on as many teams as you want.
A: Yes, you can.
A: Permission Levels are the set of permissions a user/team has. Note that Permission Levels can be given to both individual users, as well as teams. More information can be found here.
A: Admin permission gives the team/collaborator the ability to modify (add/remove/change) the access rights of their repository and thereby give rights to organization members as well as organization teams. Admin permission also gives the team/collaborator the write permission.
A: Write permission gives the team/collaborator the ability to read, clone, and push to the repository.
A: Read permission gives the team/collaborator the ability to read and clone the repository.
A: Projects help you organize and prioritize your work. Projects are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. Cards can be moved from column to column and reordered according to your needs. More information can be found here{:target="_blank"}.
A: Organization projects can be viewed and edited by any member within the organization. Team projects can be viewed by any member within a team and edited by any member within that team that has write or admin permissions.