| | 1 | Here's a current list of "component" names. Each ticket belongs to one of |
| | 2 | them. The definitions are somewhat arbitrary and non-orthogonal, but represent what I (warner) |
| | 3 | have been using to classify various issues. |
| | 4 | |
| | 5 | First, the non-code things. |
| | 6 | |
| | 7 | * '''contrib''': problems with non-core things that live in the |
| | 8 | source:contrib/ directory, like the various FUSE implementations. |
| | 9 | * '''dev-infrastructure''': things that help us build Tahoe, like the |
| | 10 | buildbot, the automated speed/memory/code-coverage tests (and the web |
| | 11 | pages which display their results), the IRC channels and mailing lists, |
| | 12 | and this Trac bugtracker itself. |
| | 13 | * '''operational''': things involved in running a Tahoe grid, external tools |
| | 14 | used to monitor or maintain a grid, tools used to launch a tahoe node, |
| | 15 | issues with te allmydata.com grid. |
| | 16 | * '''website''': things about the allmydata.org website and its Trac |
| | 17 | instance |
| | 18 | * '''unknown''': not yet categorized. All tickets default to this component |
| | 19 | until someone updates it. |
| | 20 | |
| | 21 | Now, the tickets that can be resolved by changing something in the Tahoe |
| | 22 | source code tree: |
| | 23 | |
| | 24 | * '''code''': catch-all for anything that isn't classified better. Having a |
| | 25 | lot of tickets here suggests that maybe we need to add a component or two. |
| | 26 | * '''code-dirnodes''': anything involving tahoe directories |
| | 27 | * '''code-encoding''': immutable-file encoding format/layout, cap format, |
| | 28 | encoding/decoding algorithms |
| | 29 | * frontend stuff |
| | 30 | * '''code-frontend''': general frontend things: new user-facing |
| | 31 | interfaces, FTP/SFTP servers, FUSE-like interfaces |
| | 32 | * '''code-frontend-cli''': CLI tools |
| | 33 | * '''code-frontend-w32''': windows frontend stuff |
| | 34 | * '''code-frontend-web''': webapi interfaces, user-facing "WUI" interfaces |
| | 35 | * '''code-mutable''': anything involving mutable files: encoding/decoding, |
| | 36 | share format |
| | 37 | * '''code-network''': introducer, locating storage servers, |
| | 38 | establishing/maintaining connections to them |
| | 39 | * '''code-nodeadmin''': node startup/shutdown, tools to create nodes, |
| | 40 | logging tools, management/monitoring tools, manhole, disk-space-limiting |
| | 41 | tools |
| | 42 | * '''code-peerselection''': server selection/sorting algorithm, rebalancing |
| | 43 | code, allocation policy, swarming-download |
| | 44 | * '''code-storage''': storage server implementation, share-storage |
| | 45 | directory layout, client-to-server share transfer protocol |
| | 46 | * '''documentation''': (deprecated, use docs keyword) |
| | 47 | * '''packaging''': setup.py script, library dependencies, creation of |
| | 48 | binary packages (deb/rpm/exe), licensing, installation instructions |
