Dev

Views into the process of Tahoe 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

Developer Docs

• the docs/ directory <-- most core doc is in the source tree here
• Capabilities: help to clear up confusion about readcaps and writecaps and verifycaps, etc
• PatchReviewProcess <-- You can help!

Community

• The tahoe-dev mailing list is the community forum for discussion of Tahoe design, implementation, and usage.
• Tahoe hackers chat on ​irc.freenode.net in channel #tahoe.
• The CREDITS file​ contains names people who have contributed to the Tahoe project.
• The RelatedProjects page has extensions to Tahoe and integrations of Tahoe with other open source software.
• Google Summer of Code Ideas (historical, from GSoC 2009)

Extensions

• Tahoe 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 node programmatically.
• The Extension Page lists extension projects and extension development resources.

Source Code

• Sources for Tahoe 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/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. See the BuildbotPolicy 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.
• The Packaging page shows our currently policy for how to re-use 3rd-party libraries and how to distribute Tahoe to users.
• How to Submit Patches
• CodingStandards
• ViewTickets

Metrics

• The Performance page has notes and graphs about performance measurements.
• The TestGrid page contains usage statistics about the public test grid.
• The VolunteerGrid page is about the newly created grid of servers contributed by community members.

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 is a potential topic of interest.
• TahoeVsDebianBuggyOpenSsl for details about Tahoe's mild vulnerability to the recent (May 2008) Debian OpenSSL problems.

Related Projects

• ​Foolscap -- Python remote objects done right.
• zfec -- erasure coding library and command-line tool.
• pycryptopp -- Python wrappers for the Crypto++ library.