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.
SysAdminOneMachine -- using arch for version control of configuration files for one machine
SysAdminManyMachines -- using arch for version control of configuration files for many machines
LoneProgrammer -- one programmer working alone on one project
ProgrammingTeam -- a tightly-knit programming team working together on a single project
MultiTeamProject -- several teams in different organizations working on different aspects of a project
LocalVersion -- maintaining a local version of a project published elsewhere
SmallFreeSoftwareProject -- one main developer accepting contributions from untrusted external sources
LargeFreeSoftwareProject -- several trusted developers, some contributions from untrusted sources