= Documentation =

== The Basics ==
 * [source:docs/architecture.txt architecture.txt], explaining the design decisions that have given the grid its current shape
 * [wiki:UseCases UseCases], enumerating the ways in which Tahoe should be useful
 * [source:docs/webapi.txt webapi.txt], containing everything you need to know to use Tahoe from your own program
 * [source:roadmap.txt roadmap.txt], showing how the functionality has been incrementally improved so far, and what improvements we plan to make next
 * [source:docs/codemap.txt codemap.txt], laying out the software design and the organization of the source code

== The Parade of Release Notes ==
 * [source:relnotes.txt@686 the release notes] announcing v0.2, the first public release, on May 2, 2007 and giving a general overview of why the Tahoe project exists
 * [source:relnotes.txt@790 the release notes] announcing v0.3 on June 6, 2007, including improved basic functionality
 * [source:relnotes.txt@864 the release notes] announcing v0.4 on June 29, 2007, including the new mutable, shareable, private directories
 * [source:relnotes.txt@1129 the release notes] announcing v0.5 on August 17, 2007, including the Web API and the command-line interface
 * [source:relnotes.txt@1154 the release notes] announcing v0.5.1 on August 23, 2007, fixing a security problem in the Web API
 * [source:relnotes.txt@1346 the release notes] announcing v0.6 on September 24, 2007, including improved performance and packaging

== Detailed Design Docs ==
 * FileEncoding, explaining how we turn files into shares, with verifiable hashes; This is mostly concerned with chunking and Merkle trees.
 * ShareEncoding, explaining how we turn a chunk into shares: Reed-Solomon, FEC, that stuff

== Outstanding Issues ==
 * [wiki:PeerSelection PeerSelection], explaining how a Tahoe node chooses which other nodes to use for uploading and downloading files (which raises some unsolved issues in balancing scalability, robustness, performance, and simplicity)  
 * ChangingFilesWhileCopyingThem : what are the semantics of the "upload" action? the upload takes
   non-zero time: what happens if the file is changed during that time?