= 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. * [/cgi-bin/mailman/listinfo/tahoe-dev 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. * [wiki:Doc 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. * [http://allmydata.org/trac/tahoe/query?status=new&status=assigned&status=reopened&groupdesc=1&group=priority&component=code&milestone=0.5.0&order=priority 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). * [http://allmydata.org/darcs.cgi/tahoe/?c=browse The darcs patch browser] allows you to answer questions like "Which lines did this patch change?" and "Which patches changed this line?". * [/tahoe-figleaf/current The code coverage statistics] show which lines of code get exercised by the unit tests. * [/tahoe-figleaf Archived data] is also available. * [/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_figleaf.html This graph] shows how code coverage has changed over time, measuring what percentage of the [source:src/allmydata allmydata] codebase is covered. * [/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_figleaf2.html This one] measures the number of lines that are '''not''' covered, which gives better resolution than the percentage-wise graph. * [/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_memstats.html Memory footprint] measures how much memory is consumed during basic upload operations. * [wiki:TestGrid The TestGrid page] contains usage statistics about the public test grid. * [wiki:Packaging 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 irc.freenode.net. For historical reasons, we tend to gather in channel #mnet, but probably we will eventually move to channel #tahoe. = See Also = * [wiki:News The News page] for sources of news and information. * [wiki:Bibliography The Bibliography page] contains links to scientific papers of interest. * [wiki:RelatedProjects The RelatedProjects page] contains links to a few other decentralized storage projects that you might be interested in.