Skip to content
Snippets Groups Projects
Commit 26b1ff81 authored by areynold's avatar areynold
Browse files

summarize required action

parent fecff2f4
No related branches found
No related tags found
1 merge request!11-pager draft proposal
This commit is part of merge request !1. Comments created here will be created in the context of that merge request.
......@@ -2,6 +2,10 @@
## Summary
The University of Illinois should launch a campuswide git service in order to model real world best practice and to remain competitive with its peers. This initiative requires strong backing from campus IT leadership in order to exercise due diligence, ensure interdepartmental cooperation, and authorize release of funds.
## Background
Today's university environment runs on code. From coursework to administration to research and innovation, a robust version control system (VCS) is the bedrock tool in any software development workflow, and git-based version control is the industry standard[1]. Employers expect new Computer Science graduates to have experience using GitHub[2], a leading cloud-based git service. Our academic peers have incorporated git into their classrooms for years[3] [4]. Campus computing organizations offer git training alongside sessions on campus IT orientation, data management, and popular programming languages[5]. Campus IT Pros use git to manage their codebases and also as a learning tool, sharing code snippets and suggestions in order to benefit from each other's experience.
Despite git's ubiquity, the University of Illinois does not offer a campus- or university-level git-based version control service. The closest available option is AITS Subversion[6], which does not support git, nor does it offer the kinds of features commonly found and expected in popular, modern git services[7] [8] [9]. This void has fragmented the campus version control landscape. Though some units do use AITS subversion, many others find this an unsuitable solution. Some units purchase a license and host their own git service, duplicating costs across units; others use cloud-based vendor services, storing University assets offsite; still others, particularly small units and cross-campus affinity groups, simply do without. The net effect is an enormous cost in money, time, and opportunity, with substantial business continuity risks.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment