In collaboration with IT Services, the RSE team is providing limited early access to the University’s Github Enterprise. This is to allow researchers and academics to get the full benefits of Github Enterprise now while allowing us to obtain feedback which will be used to refine the service offering in the eventual university-wide rollout.
If you would like to be a part of this program, please read through the access policy below and apply using the button at the bottom of the page.
To encourage sharing and collaboration, with permission of the Github Organisation owner, there are no restrictions on who can be allowed access to repositories (have read and write permission) under UoS Github Enterprise. Anyone that is not a member of UoS should be marked as an external collaborator.
All repositories under UoS Github Enterprise must be owned by a member of UoS, with the permission of the owner or their delegates of the Github Organisation in which it belongs to.
All Github Organisations under UoS Github Enterprise must be owned by a staff or academic within the UoS. The owner of the Github Organisation may delegate their administrative responsibilities to other members of the Github Organisation who is also a member of UoS.
Github Organisations are co-owned by the UoS Enterprise Administration team for the purposes of support, administration and auditing only; the UoS Enterprise Administration team are exempt from the responsibilities stated in the “Responsibilities of Github Organisation Owners” section.
There are no restrictions on the purpose of Github Organisations under UoS Enterprise; they can be created to represent various organisational levels within the University such as a specific course, project, research group, departmental/school, faculty or university wide.
It is the responsibility of the Github Organisation owners to manage their own members and repositories, and act in compliance with the following Github and the University’s Terms of Service and Code of conduct:
They are also responsible for the following:
The owner of a Github Organisation must ensure that all members and collaborators meet the criteria under the “Eligibility” section.
The owner of the Github Organisation must ensure that all repositories under their Github Organisation meet the criteria under the “Eligibility” section.
Should a member of a Github Organisation leave the research group or the University, their access permissions must be reviewed accordingly. Access to Github Organisation should be removed if the member no longer has need to access the contents of repositories within the organisation. The leaver’s private repositories within a Github Organisation should either be deleted, transferred to the owner or another eligible member of the organisation, or transferred to the UoS Github Enterprise Administration team for archival purposes.
Should the owner of a Github Organisation leave the University, the ownership of the organisation must be transferred to an eligible member of UoS or transferred under management of the UoS Enterprise Administration team if there are no eligible members and it is in the interests of the University to retain the organisation. Otherwise the organisation should be deleted along with its contents.
A yearly audit is performed by the UoS Enterprise Administration team to ensure access and ownership is in compliance with the Eligibility criteria. Organisations which are no longer in use and do not contain repositories kept for archival purposes should be removed. The owner of the Github Organisation will work with the UoS Enterprise Administration to facilitate the process.
Due to limitations in availability of number of seats and github runner time, the owner of a Github Organisation must comply with access and usage warnings given by the UoS Enterprise Administration team. The UoS Enterprise Administration team reserves the right to restrict access and usage of GH Organisations in case of non-compliance.
Users should expect changes to the policy and service delivery during the early access program. The UoS Enterprise Administration team will ensure that organisation owners are contacted at least two weeks ahead of upcoming changes.
UoS Github Enterprise Administration team will be using various means to collect feedback including feedback forms and directly contacting organisation owners. It is also possible provide feedback directly to github-enterpise-admin-group@sheffield.ac.uk.
Various channels of communication are available:
A new Github Organisation will be created on UoS Github enterprise with you as its owner. It is then the responsibility of the organisation’s owner and its administrators to manage their own teams and repositories within the organisation in compliance with the access policy above.
Instead of creating a new organisation, existing organisations can be migrated into UoS Github Enterprise when applying using the request form link below. The migrated organisation should be made compliant to the access policy by the first audit that will happen roughly a year after the migration.
For queries relating to collaborating with the RSE team on projects: rse@sheffield.ac.uk
Information and access to JADE II and Bede.
Join our mailing list so as to be notified when we advertise talks and workshops by subscribing to this Google Group.
Queries regarding free research computing support/guidance should be raised via our Code clinic or directed to the University IT helpdesk.