Learning patterns/Git repository for software
A learning pattern forOnline engagement patterns
created on17 September, 2014
What problem does this solve?Edit
- Non-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?Edit
Git and having a repository online, publicly available.
- 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.
- GitHub Desktop is an easy, GUI-based tool for new users who are unfamiliar with Git commands. This may reduce the learning curve involved.
When to useEdit
- Almost all bigger successful opensource projects host their source code with either git or SVN now: MediaWiki, DokuWiki, WordPress, Drupal.
- GitHub is especially useful, as it does not only enable version control and external contributions, but also a lightweight yet effective system to manage technical activities. It also integrates issue tracking and feature requests, providing a platform for developers, volunteers, and users to collaborate.
- Source control (whether Git or any other modern system) is essential for open, participatory technology. Asaf (WMF) (talk) 07:46, 8 November 2014 (UTC)
- The WIGI project uses git, github specifically, for code control. One thing that allows us to be really integrated is that using the "issues" and "milestones" features, we conduct all our project management there as well as code collaboration. Maximilianklein (talk) 22:01, 21 August 2015 (UTC)
- The StrepHit codebase is on GitHub as well. Hjfocs (talk) 14:11, 11 April 2016 (UTC)
- And the Wiki Needs Pictures one too. --AlessioMela (talk) 13:52, 5 August 2016 (UTC)
- The Wikimedia Commons app for Android uses GitHub for source code management and collaboration. Misaochan (talk) 03:49, 3 October 2016 (UTC)
- The Wikidata & ETL project uses GitHub for developing a Wikibase loader component in LinkedPipes ETL. Jakub.klimek (talk) 11:58, 1 August 2019 (UTC)
- If you're writing a MediaWiki component, using Wikimedia's gerrit specifically is also a great way to get it hooked up to TWN for automatically updated translations. Plus a lot of us do check code search to see what all is using particular things in the code. It's helpful for us because we can sometimes see new examples how to do things, and it's also at times useful for you because then we may just fix your thing too when changing some core function it uses, or the like. -— Isarra ༆ 16:37, 31 August 2019 (UTC)