= Dev =

Views into the process of Tahoe hackery.

 * Run '''{{{darcs get http://allmydata.org/source/tahoe/trunk tahoe}}}''' to grab a copy of the source code.

 * The [/cgi-bin/mailman/listinfo/tahoe-dev tahoe-dev] mailing list is the community forum for discussion of Tahoe design, implementation, and usage.

 * The [http://allmydata.org/buildbot/ buildbot] page shows current build and test results.

 * The [wiki:Doc Doc] page contains extensive documentation, which is very useful guide for hacking.
 
 * The Timeline (linked at the top of each page) has extensive details about changes to the source code, the issue tickets, and the wiki (i.e. this web site).

 * The [http://allmydata.org/darcs.cgi/tahoe/?c=browse darcs patch browser] allows you to answer questions like "Which lines did this patch change?" and "Which patches changed this line?".

 * The [/tahoe-figleaf/current code coverage statistics] show which lines of code get exercised by the unit tests.
   * [/tahoe-figleaf Archived data] is also available.
   * So is a [/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_figleaf.html graph of code coverage over time].

 * The TestGrid page contains usage statistics about the public test grid.

 * The [wiki:Bibliography Bibliography] page contains links to scientific papers of interest.

 * The [wiki:Packaging Packaging] page shows our currently policy for how to re-use 3rd-party libraries and how to distribute Tahoe to users.

= See Also = 

 * The [wiki:News News] page for sources of news and information.

 * [http://allmydata.org/trac/tahoe/query?status=new&status=assigned&status=reopened&groupdesc=1&group=priority&component=code&milestone=0.5.0&order=priority tickets] to be fixed by the next release