Utilities and best practices (according to me) related to the Fossil SCM ticket system.

I use fossil as my currently preferred version control system for both personal and customer projects. Our typical project is fairly small, with perhaps two or three active developers. Due to fossil's design goal of "low ceremony", it works exceptionally well at that scale. Naturally, fossil scales up well too, but my personal projects have not needed to push that envelope.

We are largely a Windows shop, but nothing in this repository is intended to be restricted to use with Windows. That said, little has likely been tested outside of windows. Your mileage may vary. Bug reports welcome. Etc.

<h1>Tools</h1>

  *  Reporter. This is a template-driven PDF report generator for ticket reports. Clone this repository, then look in the reporter folder for reporter.lua, sample.report, and readme.pdf (or readme.md, which can be turned into a PDF with Pandoc).


<h1>Prerequisite Tools</h1>

  *  is why we are here.
  *  is a compact (but fast and powerful) scripting language. The reporter utility is written in Lua. Any distribution for your platform of choice should work. We currently like for Windows] on Windows.
  *  AT&T for visualization of graphs and flows.
  *  for document conversions between markdown, html, and TeX.


<h1>Useful Internal Links</h1>

  *  [/wcontent|List of all wiki pages]
  *  [/wikiedit?name=Ticket+Utilities+and+Practice|Edit this page]