Dev

Views into the process of Tahoe hackery.

The Most Important Parts

• Run darcs get http://allmydata.org/source/tahoe/trunk tahoe to grab a copy of the source code.

• The tahoe-dev mailing list is the community forum for discussion of Tahoe design, implementation, and usage.

• The Buildbot page (linked at the top of each page) shows current build and test results.

• The Doc page contains extensive documentation, which is very useful guide for hacking. See especially the webapi.txt document, which shows how to control a Tahoe node programmatically.

• ​The tickets to be fixed for the v0.5 release.

More Good Stuff For Hackers

• The Timeline (linked at the top of each page) has extensive details about changes to the source code, the issue tickets, and the wiki (i.e. this web site).

• ​The darcs patch browser allows you to answer questions like "Which lines did this patch change?" and "Which patches changed this line?".

• The code coverage statistics show which lines of code get exercised by the unit tests.
  • Archived data is also available.
  • This graph shows how code coverage has changed over time, measuring what percentage of the allmydata codebase is covered.
  • This one measures the number of lines that are not covered, which gives better resolution than the percentage-wise graph.
• Memory footprint measures how much memory is consumed during basic upload operations.

• The TestGrid page contains usage statistics about the public test grid.

• The Packaging page shows our currently policy for how to re-use 3rd-party libraries and how to distribute Tahoe to users.

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.