= Dev =

Views into the process of Tahoe-LAFS hackery.
 * 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 User Doc page]

= Sauce =

 * Darcs checkout: "darcs get --lazy http://tahoe-lafs.org/source/tahoe-lafs/trunk tahoe-lafs"
 * git checkout "http://tahoe-lafs.org/pipermail/tahoe-dev/2010-October/005408.html" EXPERIMENTAL!: "git clone git://github.com/warner/tahoe-lafs.git"

== Community ==

 * [/../../cgi-bin/mailman/listinfo/tahoe-dev The tahoe-dev mailing list] is the community forum for discussion of Tahoe-LAFS design, implementation, and usage.
 * Tahoe-LAFS hackers chat on [irc://irc.freenode.net/%23tahoe-lafs irc.freenode.net in channel #tahoe-lafs].
 * [source:CREDITS The CREDITS file] contains names people who have contributed to the Tahoe-LAFS project.
 * [wiki:RelatedProjects The RelatedProjects page] has extensions to Tahoe-LAFS and integrations of Tahoe-LAFS with other open source software.

== Extensions ==

 * Tahoe-LAFS has a programmatic API which enables building custom applications on top of the storage infrastructure.
 * The [source:docs/frontends/webapi.txt docs/frontends/webapi.txt] document shows how to control a Tahoe-LAFS node programmatically.
 * [wiki:Extensions The Extension Page] lists extension projects and extension development resources. (WAIT: How is this different from the RelatedProjects page? --Zooko 2010-06-16)

== Developer Docs ==
 * [source:docs/ the docs/ directory] <-- most core doc is in the source tree here
 * [wiki:Capabilities]: what are readcaps and writecaps and verifycaps, etc
 * [wiki:PatchReviewProcess How to review patches] <-- You can help!
 * [wiki:Patches How to submit patches]
 * [wiki:CodingStandards How to write code]
 * [wiki:Packaging The Packaging page] shows our currently policy for how to re-use 3rd-party libraries and how to distribute Tahoe-LAFS to users.
 * [wiki:OneHundredYearCryptography]

== Tools ==
  * [http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-lafs-trac-stream tahoe-lafs-trac-stream] mailing list is the way to receive lots of emails from trac
 * [wiki:ViewTickets]
 * Sources for Tahoe-LAFS and its side-projects are browsable via the "Browse Source" button at the top of each [http://allmydata.org/trac project site]
 * To fetch the source code using [http://darcs.net darcs v2]: {{{darcs get --lazy http://allmydata.org/source/tahoe-lafs/trunk tahoe-lafs}}}
  * {{{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}}}.
 * there is an experimental git mirror of the darcs repository (not necessarily up-to-date) [http://github.com/warner/tahoe-lafs on github].
 * 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.  See the BuildbotPolicy page and [wiki:HowtoContributeABuildbot] page.
 * 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).
 * [/../../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.

== 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.
 * [wiki:ResearchVenues The ResearchVenues page] contains a list of conferences and other venues where Tahoe-LAFS is a potential topic of interest.
 * TahoeVsDebianBuggyOpenSsl for details about Tahoe-LAFS's mild vulnerability to
   the recent (May 2008) Debian OpenSSL problems.
 * [wiki:GSoCIdeas Google Summer of Code Ideas]