Reorganize into a deeper hierarchy, and punt some "Most Important" items into more specific categories.
[Imported from Trac: page Dev, version 37]
parent
33970e95e0
commit
e0bc7f52bc
29
Dev.md
29
Dev.md
|
@ -6,17 +6,28 @@ Views into the process of Tahoe hackery.
|
|||
|
||||
* 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.
|
||||
|
||||
* The Roadmap page (linked at the top of each page) shows the next planned release and what improvements and bugfixes we are working on.
|
||||
* Tahoe hackers chat on irc.freenode.net. For historical reasons, we tend to gather in channel #mnet.
|
||||
|
||||
## Extensions
|
||||
|
||||
* Tahoe has a programmatic API which simplifies building custom applications on top of the storage infrastructure.
|
||||
|
||||
* The **webapi.txt** document shows how to control a Tahoe node programmatically.
|
||||
|
||||
|
||||
## Repository Resources
|
||||
|
||||
* 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 Doc page](Doc) 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 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?".
|
||||
|
||||
|
@ -25,14 +36,14 @@ Views into the process of Tahoe hackery.
|
|||
* [/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.
|
||||
|
||||
* [The Packaging page](Packaging) 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.
|
||||
|
||||
# See Also
|
||||
|
||||
* [The News page](News) for sources of news and information.
|
||||
|
|
Loading…
Reference in a new issue