Distributed project control management: using Fossil to get beyond source control

Effective source control practices are a requirement for most team software projects. For a great majority of these, web publishing, issue tracking, documentation maintenance, development news/blogs, and more are similarly critical. Engineers set out to choose from among several tools to support each of these project activities, find ways to integrate them, and, when possible, synchronize their histories, but this is not a trivial task. Typically, source control management is one of the first development support technologies selected, and with student teams and many open source projects it is often the last. Efforts to get a web site published and integrated with issue tracking and wiki systems quickly dissolve into good intentions as work toward them begins to be perceived as negatively impacting code inertia.