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.
• 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

• The tahoe-dev mailing list is the community forum for discussion of Tahoe-LAFS design, implementation, and usage.
• Tahoe-LAFS hackers chat on ​irc.freenode.net in channel #tahoe-lafs.
• The CREDITS file​ contains names people who have contributed to the Tahoe-LAFS project.
• 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 docs/frontends/webapi.txt document shows how to control a Tahoe-LAFS node programmatically.
• 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

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

Tools

• ​tahoe-lafs-trac-stream mailing list is the way to receive lots of emails from trac

• ViewTickets
• Sources for Tahoe-LAFS and its side-projects are browsable via the "Browse Source" button at the top of each ​project site
• To fetch the source code using ​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) ​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 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).
• The code coverage statistics show which lines of code get exercised by the unit tests.
  • Archived data is also available.
  • This graph measures the number of lines that are not covered.

Metrics

• The Performance page has notes and graphs about performance measurements.
• The TestGrid page contains usage statistics about the public test grid.

See Also

• The News page for sources of news and information.
• The Bibliography page contains links to scientific papers of interest.
• The RelatedProjects page contains links to a few other decentralized storage projects that you might be interested in.
• 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.
• Google Summer of Code Ideas