Versioning strategies
Sometimes reading through the tutorial and command details for Arch can keep you from seeing the forest for all the trees. Arch has incredible flexibility in the way one person or a group of people can use it. But despite that flexibility, there are still some mainline cases for how programming teams, lone programmers, system administrators and others will want to use the software.
The following set of versioning strategies outlines some of the ways that people use version control software, and how Arch can meet those needs.
Strategy/Sysadmin One Machine -- using Arch for version control of configuration files for one machine
Strategy/Sysadmin Many Machines -- using Arch for version control of configuration files for many machines
Strategy/Lone Programmer -- one programmer working alone on one project
Strategy/Programming Team -- a tightly-knit programming team working together on a single project
Strategy/Multi Team Project -- several teams in different organizations working on different aspects of a project
Strategy/Local Version -- maintaining a local version of a project published elsewhere
Strategy/Small Free Software Project -- one main developer accepting contributions from untrusted external sources
Strategy/Large Free Software Project -- several trusted developers, some contributions from untrusted sources