1-pager draft proposal
Summary
Adds a general purpose, high level proposal intended to establish the broad need for a campus-level git service. Takes benefit to programmers as a given, and focuses instead on value to students and faculty. Does not cover implementation details, which would be handled in a future phase/proposal. Intended audience is department-level decision makers who could authorize further investigation.
Review needs
- Impact
- Does the proposal make a convincing case that a shared git service would be beneficial to students, faculty, and staff?
- Can assertions be backed up by faculty statements or public data?
- Wordsmithing
- Check for readability
- Minimize jargon
- Add a snappy title
- Sources
- I lean heavily on github's blogs. Can sources be diversified?
- Do footnotes match references appropriately?