= 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://irc.freenode.net/%23tahoe irc.freenode.net in channel #tahoe].
 * [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 ==

 * To fetch the source code using [http://darcs.net darcs v2]: {{{darcs get --lazy http://allmydata.org/source/tahoe/trunk-hashedformat tahoe}}}
  * {{{darcs v2}}} is highly recommended over {{{darcs v1}}}.  If you really don't want to install {{{darcs v2}}}, then you can use {{{darcs v1}}} instead, but you'll have to run a slightly different command-line and be prepared to wait for tens of minutes for the initial {{{get}}} to finish.  The command-line for {{{darcs v1}}} is: {{{darcs get http://allmydata.org/source/tahoe/trunk-darcs1format tahoe}}}.
 * 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_figleaf2.html This graph] measures the number of lines that are '''not''' covered.
 * [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.
 * TahoeVsDebianBuggyOpenSsl for details about Tahoe's mild vulnerability to
   the recent (May 2008) Debian OpenSSL problems.

== Related Projects ==
 * [http://foolscap.lothar.com Foolscap] -- Python remote objects done right.
 * [/../zfec zfec] -- erasure coding library and command-line tool.
 * [/../pycryptopp pycryptopp] -- Python wrappers for the Crypto++ library.