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

add tahoe-lafs-trac-stream mailing list and reorg a bit 

[Imported from Trac: page Dev, version 87]
zooko 2010-06-17 04:50:25 +00:00
parent 28cd3b215d
commit f6298a41d5
1 changed files with 8 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
Dev.md

@ -9,13 +9,13 @@ Views into the process of Tahoe hackery.
* [/../../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 in channel #tahoe-lafs]irc://irc.freenode.net/%23tahoe.
* [The CREDITS file]source:CREDITS contains names people who have contributed to the Tahoe project.
* [The [RelatedProjects](RelatedProjects) page](RelatedProjects) has extensions to Tahoe and integrations of Tahoe with other open source software.
* [The [RelatedProjects](RelatedProjects) page](RelatedProjects) has extensions to Tahoe-LAFS and integrations of Tahoe-LAFS with other open source software.
## Extensions
* Tahoe has a programmatic API which enables building custom applications on top of the storage infrastructure.
* The [docs/frontends/webapi.txt]source:docs/frontends/webapi.txt document shows how to control a Tahoe node programmatically.
* [The Extension Page](Extensions) lists extension projects and extension development resources.
* Tahoe-LAFS has a programmatic API which enables building custom applications on top of the storage infrastructure.
* The [docs/frontends/webapi.txt]source:docs/frontends/webapi.txt document shows how to control a Tahoe-LAFS node programmatically.
* [The Extension Page](Extensions) lists extension projects and extension development resources. (WAIT: How is this different from the [RelatedProjects](RelatedProjects) page? --Zooko 2010-06-16)
## Developer Docs
* [the docs/ directory]source:docs/ <-- most core doc is in the source tree here
@ -23,6 +23,10 @@ Views into the process of Tahoe hackery.
* [How to review patches](PatchReviewProcess) <-- You can help!
* [How to Submit Patches](Patches)
* [CodingStandards](CodingStandards)
* [The Packaging page](Packaging) shows our currently policy for how to re-use 3rd-party libraries and how to distribute Tahoe to users.
## Tools
* [tahoe-lafs-trac-stream](http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-lafs-trac-stream) mailing list is the way to receive lots of emails from trac
* [ViewTickets](ViewTickets)
* Sources for Tahoe and its side-projects are browsable via the "Browse Source" button at the top of each [project site](http://allmydata.org/trac)
* To fetch the source code using [darcs v2](http://darcs.net): `darcs get --lazy <http://allmydata.org/source/tahoe-lafs/trunk> tahoe-lafs`
@ -33,7 +37,6 @@ Views into the process of Tahoe hackery.
* [/../../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.
* [The Packaging page](Packaging) shows our currently policy for how to re-use 3rd-party libraries and how to distribute Tahoe to users.
## Metrics