Gitlab (https://code.oakland.edu) is a source code management and collaboration software that is hosted and operated by Oakland University Technology Services (UTS). Gitlab is available to use for Oakland University staff and faculty with a valid NetID.
This resource is only available on-campus and not available to computers outside of the Oakland University network. There are many other resources available online as a cloud-based solution, although Gitlab should be considered if you have concerns over intellectual property and security.
Oakland University currently runs the Community Edition of Gitlab with available documentation at http://doc.gitlab.com/ce/.
Oakland University’s Gitlab is only available for official University source code and not personal or student course work. Requests can be made to firstname.lastname@example.org to allow developers access to create their own repositories within Oakland University’s Gitlab service.
Policies and Guidelines
The Gitlab service (https://code.oakland.edu) is provided as a “Good Will Service” with no guarantee of service availability. UTS will provide access and disaster recovery services only.
By accessing and using these resources you agree to use all information technology resources responsibly and in compliance with University policies and guidelines (http://www.oakland.edu/uts/policies).
As a general guideline, do not store any Confidential Data (as defined in university Policy #860 Information Security) or other security related data in the repositories, such as personal data, passwords, and SSL keys. These generally should be kept in a separate and secure location.
When requesting access, please send the following in an email to email@example.com , subject GITLAB Request:
- List of developers needing access
- Purpose of repositories
- Estimated size of repository data and growth rates per annum
- Point of contact that can sign off on usage
Gitlab Services Provided
- Git Repositories
Developer Access Controls (More Information https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/permissions/permissions.md)
- Issue Tracker
- File Browser
- Activity Stream
- Pull Requests
- Code Snippets
- Web Hooks
References and Best Practices
- Gitlab does recommend keeping a project under 1GB to maintain performance and it does list the size of the projects in the administrative view.
Development Work Flow - https://about.gitlab.com/2014/09/29/gitlab-flow/
Git Best Practices - https://sethrobertson.github.io/GitBestPractices/
Virtual Git Reference - http://marklodato.github.io/visual-git-guide/index-en.html