wiki:Dev

Version 61 (modified by zooko, at 2009-01-08T05:20:59Z) (diff)

--

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.
  • The Doc page contains extensive documentation, which is very useful guide for hacking.

Community

Extensions

  • Tahoe has a programmatic API which enables building custom applications on top of the storage infrastructure.
  • The webapi.txt document shows how to control a Tahoe node programmatically.
  • The Extension Page lists extension projects and extension development resources.

Source Code

  • Run darcs get --lazy http://allmydata.org/source/tahoe/trunk-hashedformat tahoe to grab a copy of the source code using darcs v2. 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: darcs get http://allmydata.org/source/tahoe/trunk 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).
  • 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.
  • 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

Metrics

See Also

Related Projects

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