This framing project holds parts of my professional and hobby programming curriculum I wish to share. It is well-maintained by design, as the copies I use daily are symbolically linked from a repository working copy. If you find some items useful or are gifted with ideas, feel free to comment or even contribute!

The final structure would approximate the following. Each subproject has the following:

• source code (in NAME/src);
• tests (under NAME/test, unit, integration);
• wiki pages with documentation (user, developer, screenshots);
• a bugtracker (section) for TODOs;
• a combined developer's and basic support mailing list (section);
• scripts for testing, building and releasing (maybe these could be held by their respective projects).

I'm still not decided on how to manage the projects as a whole, though. At present, the following conventions sound reasonable:

• a single repository for all projects;
• develop in trunk;
• branch in trunk if a common library can be extracted and specialized versions are needed;
• each project has an associated component marking in the bugtracker;
• a distinct tag or subject prefix in the mailing list;
• each source directory contains a subdirectory with tests.

Note that the '''volatile''' directory should change a lot in the future, so do keep an eye on it. Other folders ought to be stable, once migrated from volatile. At present, it only holds sources in plain subdirecteries.