Introduction

Most people have write permission to only the few FOLIO repositories that they regularly work on via their GitHub Teams. For contributions to any other repository they will need to “fork” it to their personal GitHub account (refer to contribution guidelines).

GitHub new developer

For new developers (i.e. not yet a member of “folio-org” organization) we ask that a project manager (see Team and module responsibility matrix) or at least a known existing developer, makes this request.

They need to either request on the #devops Slack channel, or raise a FOLIO DevOps Jira ticket. Especially do the latter with a group of new people.

Please do not clone old tickets. It just tends to make a mess by applying old settings, and re-sending irrelevant old notifications.

Provide the GitHub username (i.e. account name) of the new developer, so that we can be absolutely sure that we are inviting the correct person. Provide a link to their GitHub profile page, which is also a double-check that you are telling us the correct person.

Specify which GitHub Teams to be allocated.

The new developer will need to follow the received email and accept the invitation.

GitHub team access

Note that we try to steer clear of managing GitHub access for individuals, and instead allocate access for a whole GitHub Team to a repository.

Please clearly specify which team and which repository. It is more efficient for DevOps when you provide links to the team and repos.

Manage members for teams

The GitHub Teams each have a member who has the “Maintainer” role for that team (view the relevant Team or the Matrix). The team Maintainers can add or remove existing members. Of course, if the person is not yet a member of folio-org then follow the new developer instructions above.

If a team member leaves the FOLIO organization and will not further participate, then please contact DevOps as explained above, to remove their access.