Version 33 (modified by zooko, at 2007-09-19T22:45:00Z) (diff)

add link to Performance


Views into the process of Tahoe hackery.

The Most Important Parts

  • Run darcs get tahoe to grab a copy of the source code.
  • 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.

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 various operations.
  • The Packaging page shows our currently policy for how to re-use 3rd-party libraries and how to distribute Tahoe to users.
  • Tahoe hackers chat on For historical reasons, we tend to gather in channel #mnet.

See Also