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

remove blank space between list entries, so that the 'Dev' page link is visible without scrolling 

[Imported from Trac: page Dev, version 43]
warner 2007-10-21 21:09:26 +00:00
parent 92a6c0d3be
commit 49c3073b3f
1 changed files with 2 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
Dev.md

@ -5,52 +5,40 @@ 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 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](Doc) contains extensive documentation, which is very useful guide for hacking.
## Community
* [/cgi-bin/mailman/listinfo/tahoe-dev The tahoe-dev mailing list] is the community forum for discussion of Tahoe design, implementation, and usage.
* Tahoe hackers chat on irc.freenode.net. For historical reasons, we tend to gather in channel #mnet.
* [The CREDITS file]source:CREDITS contains names people who have contributed to the Tahoe project.
## Extensions
* Tahoe has a programmatic API which enables building custom applications on top of the storage infrastructure.
* The [/trac/tahoe/browser/docs/webapi.txt webapi.txt] document shows how to control a Tahoe node programmatically.
* [The Extension Page](Extensions) lists extension projects and extension development resources.
## Source Code Tools
* 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](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?".
* [/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 Packaging page](Packaging) shows our currently policy for how to re-use 3rd-party libraries and how to distribute Tahoe to users.
## Metrics
* [The Performance page](Performance) has notes and graphs about performance measurements.
* [The [TestGrid](TestGrid) page](TestGrid) contains usage statistics about the public test grid.
## See Also
* [The News page](News) for sources of news and information.
* [The Bibliography page](Bibliography) contains links to scientific papers of interest.
* [The [RelatedProjects](RelatedProjects) page](RelatedProjects) contains links to a few other decentralized storage projects that you might be interested in.