Learning patterns/Git repository for software: Difference between revisions
Appearance
Content deleted Content added
Bgibbs (WMF) (talk | contribs) + 9 categories using HotCat |
Bgibbs (WMF) (talk | contribs) |
||
| Line 52: | Line 52: | ||
<!--optional. a bulleted list of related patterns. See Programs:Evaluation_portal/Library#Learning_patterns for ideas--> |
<!--optional. a bulleted list of related patterns. See Programs:Evaluation_portal/Library#Learning_patterns for ideas--> |
||
*[[Grants:Learning patterns/Tracking user contributions by chapter]] |
*[[Grants:Learning patterns/Tracking user contributions by chapter]] |
||
*[[Grants:Learning patterns/Set up a GitHub profile for your hack-a-thons]] |
|||
=== External links === |
=== External links === |
||
Revision as of 04:28, 29 December 2014
A learning pattern forOnline engagement patterns
Git repository for software
problemDealing with multiple versions of software or components of it can easily become messy
solutionUsing a Git repository, having a clone of it publicly available on a service that is known for its speed and stability solves several challenges, including versionning, speed, attribution, availability and tidiness at once.
creator• Rillke
created on17 September, 2014
What problem does this solve?
- In-transparent code development using funds spent for software is disadvantageous as it does not allow tracking activity and progress by the grant maker.
- Collaborative software engineering easily becomes messy without a source code management system.
- Most source code management systems require an internet connection to submit.
- A good way to find out which solution is the best is try&fail but most source code management systems do not have the concept of offline-branches.
What is the solution?
Git and having a repository online, publicly available.
General considerations
- Git is probably less intuitive to use than SVN or other popular source code revision management systems. It comes with a lot of features but also has a steep learning curve.
- All contributors who want to contribute will have to have a basic understanding how to use Git in order to submit a patch or to clone a repo in order to test.
- Review & Merge frequently if you have multiple collaborators. Otherwise you'll run into merge conflicts and manual re-basing can consume enormous parts of your time.
When to use
- Almost all bigger successful opensource projects host their source code with either git or SVN now: MediaWiki, DokuWiki, WordPress, Drupal.
See also
Related patterns
- Grants:Learning patterns/Tracking user contributions by chapter
- Grants:Learning patterns/Set up a GitHub profile for your hack-a-thons
External links
References
Endorsements
- Source control (whether Git or any other modern system) is essential for open, participatory technology. Asaf (WMF) (talk) 07:46, 8 November 2014 (UTC)
Categories:
- Learning patterns
- Learning patterns not yet ready for translation
- Hackathon learning patterns
- Reporting patterns
- Evaluation learning patterns
- Knowledge sharing learning patterns
- Communications learning patterns
- Project management learning patterns
- Organizational effectiveness learning patterns
- Draft learning patterns
