= Dev =

Views into the process of Tahoe hackery.

== The Most Important Parts ==

 * The Roadmap page (linked at the top of each page) shows the next planned release and what improvements and bugfixes we are working on.
 * [wiki:Doc The Doc page] contains extensive documentation, which is very useful guide for hacking.

== Community ==

 * [/../../cgi-bin/mailman/listinfo/tahoe-dev The tahoe-dev mailing list] is the community forum for discussion of Tahoe design, implementation, and usage.
 * Tahoe hackers chat on irc.freenode.net.  For historical reasons, we tend to gather in channel #mnet.
 * [source:CREDITS The CREDITS file] contains names people who have contributed to the Tahoe project.

== Extensions ==

 * Tahoe has a programmatic API which enables building custom applications on top of the storage infrastructure.
 * The [source:docs/webapi.txt webapi.txt] document shows how to control a Tahoe node programmatically.
 * [wiki:Extensions The Extension Page] lists extension projects and extension development resources.

== Source Code ==

 * Run {{{darcs get http://allmydata.org/source/tahoe/trunk tahoe}}} to grab a copy of the source code using [http://darcs.net darcs].
 * http://allmydata.org/source/tahoe/tarballs/ contains snapshots of current source code.
 * The Buildbot page (linked at the top of each page) shows current build and test results.
 * The Timeline (linked at the top of each page) shows changes to the source code, the issue tickets, and the wiki (i.e. this web site).
 * [http://allmydata.org/darcs.cgi/tahoe/?c=browse The darcs patch browser] allows you to answer questions like "Which lines did this patch change?" and "Which patches changed this line?".
 * [/../../tahoe-figleaf/current The code coverage statistics] show which lines of code get exercised by the unit tests.
   * [/../../tahoe-figleaf Archived data] is also available.
   * [/../../tahoe-figleaf-graph/hanford.allmydata.com-tahoe_figleaf.html This graph] shows how code coverage has changed over time, measuring what percentage of the [source:src/allmydata allmydata] codebase is covered.
   * [/../../tahoe-figleaf-graph/hanford.allmydata.com-tahoe_figleaf2.html This one] measures the number of lines that are '''not''' covered, which gives better resolution than the percentage-wise graph.
 * [wiki:Packaging The Packaging page] shows our currently policy for how to re-use 3rd-party libraries and how to distribute Tahoe to users.
 * [wiki:Patches How to Submit Patches]

== Metrics ==

 * [wiki:Performance The Performance page] has notes and graphs about performance measurements.
 * [wiki:TestGrid The TestGrid page] contains usage statistics about the public test grid.

== See Also == 

 * [wiki:News The News page] for sources of news and information.
 * [wiki:Bibliography The Bibliography page] contains links to scientific papers of interest.
 * [wiki:RelatedProjects The RelatedProjects page] contains links to a few other decentralized storage projects that you might be interested in.

== Libraries ==
 * [/../zfec The zfec trac] is for the zfec library. There is a [/../../cgi-bin/mailman/listinfo/zfec-dev mailing list] and a [http://pypi.python.org/pypi/zfec PyPI page] as well.
 * [/../pycryptopp The pycryptopp trac] is for the pycryptopp crypto library.