= Dev = Views into the process of Tahoe-LAFS 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. * [wiki:Doc The User Doc page] = Source Code (via revision control) = * Darcs checkout: "darcs get --lazy http://tahoe-lafs.org/source/tahoe-lafs/trunk tahoe-lafs" * [https://github.com/warner/tahoe-lafs git checkout] (EXPERIMENTAL!): {{{git clone git://github.com/warner/tahoe-lafs.git}}} (announced [http://tahoe-lafs.org/pipermail/tahoe-dev/2010-October/005408.html here]) == Community == * [/../../cgi-bin/mailman/listinfo/tahoe-dev The tahoe-dev mailing list] is the community forum for discussion of Tahoe-LAFS design, implementation, and usage. * Tahoe-LAFS hackers chat on [irc://irc.freenode.net/%23tahoe-lafs irc.freenode.net in channel #tahoe-lafs]. This channel is archived at [http://fred.submusic.ch/irc/tahoe-lafs/] . * [source:CREDITS The CREDITS file] contains names people who have contributed to the Tahoe-LAFS project. * [wiki:RelatedProjects The RelatedProjects page] has extensions to Tahoe-LAFS and integrations of Tahoe-LAFS with other open source software. == Extensions == * Tahoe-LAFS has a programmatic API which enables building custom applications on top of the storage infrastructure. * The [source:docs/frontends/webapi.rst] document shows how to control a Tahoe-LAFS node programmatically over HTTP. * [wiki:Extensions The Extension Page] has some additional tips on how to use the web-API. == Developer Docs == * [source:docs/ the docs/ directory] <-- most core doc is in the source tree here * [wiki:Capabilities]: what are readcaps and writecaps and verifycaps, etc * [wiki:PatchReviewProcess How to review patches] <-- You can help! * [wiki:Patches How to submit patches] * [wiki:CodingStandards How to write code] * [wiki:Packaging The Packaging page] shows our current policy for how to re-use 3rd-party libraries and how to distribute Tahoe-LAFS to users. * [wiki:OneHundredYearCryptography] == Tools == * [http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-lafs-trac-stream tahoe-lafs-trac-stream] mailing list is the way to receive lots of emails from trac * [wiki:ViewTickets] * Sources for Tahoe-LAFS and its side-projects are browsable via the "Browse Source" button at the top of each [http://tahoe-lafs.org/trac project site] * To fetch the source code using [http://darcs.net darcs] (version 2.0 or newer): {{{darcs get --lazy http://tahoe-lafs.org/source/tahoe-lafs/trunk tahoe-lafs}}} * there is an experimental git mirror of the darcs repository (not necessarily up-to-date) [http://github.com/warner/tahoe-lafs on github]. * http://tahoe-lafs.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 and [wiki:HowtoContributeABuildbot] 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). * [/../../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_figleaf2.html This graph] measures the number of lines that are '''not''' covered. == Metrics == * [wiki:Performance The Performance page] has notes and graphs about performance measurements. * [wiki:TestGrid The TestGrid page] contains usage statistics about the public test grid. == 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. * [wiki:ResearchVenues The ResearchVenues page] contains a list of conferences and other venues where Tahoe-LAFS is a potential topic of interest. * TahoeVsDebianBuggyOpenSsl for details about Tahoe-LAFS's mild vulnerability to the recent (May 2008) Debian OpenSSL problems. * [wiki:GSoCIdeas Google Summer of Code Ideas]