tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

layout, formatting, more links, etc. 

[Imported from Trac: page Dev, version 18]
zooko 2007-07-18 22:41:03 +00:00
parent 27df77d3ac
commit 6522cec04e
1 changed files with 15 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
Dev.md

@ -2,33 +2,37 @@
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 [/cgi-bin/mailman/listinfo/tahoe-dev tahoe-dev] mailing list is the community forum for discussion of Tahoe design, implementation, and usage.
* [/cgi-bin/mailman/listinfo/tahoe-dev The tahoe-dev mailing list] is the community forum for discussion of Tahoe design, implementation, and usage.
* The page (linked at the top of each page) shows current build and test results.
* The Buildbot page (linked at the top of each page) shows current build and test results.
* The [Doc](Doc) page contains extensive documentation, which is very useful guide for hacking.
* [The Doc page](Doc) contains extensive documentation, which is very useful guide for hacking.
* [The tickets](http://allmydata.org/trac/tahoe/query?status=new&status=assigned&status=reopened&groupdesc=1&group=priority&component=code&milestone=0.5.0&order=priority) 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](http://allmydata.org/darcs.cgi/tahoe/?c=browse) allows you to answer questions like "Which lines did this patch change?" and "Which patches changed this line?".
* [The darcs patch browser](http://allmydata.org/darcs.cgi/tahoe/?c=browse) allows you to answer questions like "Which lines did this patch change?" and "Which patches changed this line?".
* The [/tahoe-figleaf/current code coverage statistics] show which lines of code get exercised by the unit tests.
* [/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 [allmydata]source:src/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
* The [TestGrid](TestGrid) page contains usage statistics about the public test grid.
* The [Packaging](Packaging) page shows our currently policy for how to re-use 3rd-party libraries and how to distribute Tahoe to users.
* [The Packaging page](Packaging) shows our currently policy for how to re-use 3rd-party libraries and how to distribute Tahoe to users.
# See Also
* The [News](News) page for sources of news and information.
* [The News page](News) for sources of news and information.
* [tickets](http://allmydata.org/trac/tahoe/query?status=new&status=assigned&status=reopened&groupdesc=1&group=priority&component=code&milestone=0.5.0&order=priority) to be fixed by the next release
* [The Bibliography page](Bibliography) contains links to scientific papers of interest.
* The [Bibliography](Bibliography) page contains links to scientific papers of interest.
* The [RelatedProjects](RelatedProjects) page contains links to a few other decentralized storage projects that you might be interested in.
* [The [RelatedProjects](RelatedProjects) page](RelatedProjects) contains links to a few other decentralized storage projects that you might be interested in.