wiki:ViewTickets

Version 215 (modified by daira, at 2013-08-13T22:55:48Z) (diff)

add 1.12 milestone

Custom Query

Special Tickets

Keywords

Each keyword links to all of the open tickets mentioning that keyword. If you find existing tickets that are missing keywords, please feel free to add them.

  • iputil (4): having to do with automatically detecting the node's own IP address
  • integrity (32): could lead to the unintended alteration of data
  • rollback (7): could lead to unauthorized rollback to an earlier version of data
  • confidentiality (28): could lead to the unintended disclosure of file contents
  • capleak (23): could lead to the unintended disclosure of capabilities
  • privacy (23): could lead to the unintended disclosure of information other than file contents (e.g. how many files of what size you access at what times, the shape of your directory graph, the fact that you run a Tahoe-LAFS client or storage server, etc.)
  • anonymity (10): relevant to running Tahoe-LAFS nodes across anonymity-enhancing protocols such as Tor and I2P (should usually also be tagged with 'privacy')
  • security (56): security issues not necessarily tagged with a more specific keyword (confidentiality, integrity, etc.)
  • preservation (44): could lead to unintended loss of (failure to preserve) data
  • availability (43): could lead to a temporary condition of being unable to read or write to the filesystem
  • reliability (38): could lead to unpredictable failure of functionality
  • anti-censorship (22): could help with resistance to censorship or denial of service
  • scalability (16): scaling to large and/or geographically dispersed storage grids, or to high traffic volumes or numbers of clients
  • location (6): concerned with location awareness -- placement of shares according to topographical, geographical, bandwidth, etc. constraints
  • forward-compatibility (24): relevant to ​forward compatibility of stored data or caps with future Tahoe versions
  • transparency (26): features that help the user see and understand the inner workings, such as visualization, statistics, explorability
  • unicode (9): related to Unicode
  • i18n (7): related to internationalization (usually also to Unicode)
  • usability (205): concerned with ease of use (interface or mental models)
  • error (103): concerned with error reporting to end-users
  • install (8): installation problems
  • docs (76): fixing this issue involves updating documentation
  • test (71): additional or better test coverage needed
  • performance (119): an opportunity to improve some aspect of performance (speed, latency, bandwidth, space usage, etc.)
  • memory (22): an opportunity to improve memory usage (should usually also be tagged with 'performance')
  • space-efficiency (14): an opportunity to improve space-efficiency of stored files
  • extensibility (4): extensibility and customization mechanisms
  • hang (15): could cause an operation to hang, either indefinitely or for long periods
  • large (8): affecting large files or directories
  • ucwe (10): an UncoordinatedWriteError is triggered when it should not be, or vice versa
  • newcaps (36): relevant to NewCapDesign
  • revocation (9): revoking an authority previously granted
  • newurls (22): relevant to improvements in encoding caps as URLs
  • firewall (11): firewall and NAT traversal issues
  • standards (16): compliance to standards (HTTP, HTML etc.)
  • heisenbug (7): bugs that are not easily reproducible so far
  • cleanup (23): code clean-up / refactoring
  • time (11): having to do with time and clocks
  • ostrom (7): having to do with Elinor Ostrom's theory of governance of the commons (as applied to Tahoe-LAFS resources such as storage service)
  • servers-of-happiness (23): having to do with the "servers of happiness" upload semantics (see ticket #778)
  • defaults (4): having to do with the default settings for configuration parameters
  • compression (4): having to do with compressing the plaintext
  • no keywords (300): open tickets with no keywords

Combined queries:

Platform keywords

See also eggs (2): tickets about building binary eggs of dependencies.

Functionality

  • helper (18): related to helper function
  • repair (38): related to repair function
  • verify (20): related to verification
  • introducer, introduction (20): related to the existing introducer, or to node introduction in general
  • upload (81): related to file upload
  • download (41): related to file download
  • cache (8): related to caching
  • alias (7): related to aliases
  • metadata (11): related to metadata
  • names (11): related to file/directory names or paths
  • leases (17): related to leases or garbage collection
  • accounting (19): related to storage accounting
  • cloud (2): related to cloud services or the cloud backend
  • logging (21): related to logging
  • ophandle (2): related to operation handles
  • statistics (28): related to usage statistics
  • http (22): related to the HTTP protocol
  • tahoe-cp (19): tahoe cp command
  • tahoe-ls (4): tahoe ls command
  • tahoe-unlink (1): tahoe unlink command
  • tahoe-mv (3): tahoe mv command
  • tahoe-check (7): tahoe check command
  • tahoe-backup (36): tahoe backup command
  • tahoe-run (1): tahoe run command
  • tahoe-* (86): all tahoe commands

Frontends and applications

  • wui (72): Web user interface
  • ftpd (7): FTP frontend
  • sftp (36): SFTP frontend
  • sshfs (9): filesystem access via sshfs
  • dokan (2): filesystem access via Dokan
  • pyfilesystem (3): pyfilesystem library (and its Dokan and TahoeLAFS interfaces)
  • fuse (10): FUSE filesystem interface
  • drop-upload (0): Drop-upload frontend
  • webdav (5): (hypothetical) WebDAV frontend
  • smb (3): SMB filesystem interface (WinFUSE)
  • jsui (4): JavaScript (probably Cajita) user interface
  • webdrive (0): allmydata.com webdrive user interface
  • iphone (0): iPhone client
  • music (2): Cloud music player
  • tiddly (10): Tiddly-on-Tahoe wiki

Dependencies

Development infrastructure

  • git (8): git revision control system
  • trac (9): trac bug tracker and wiki
  • coverage (2): test coverage analyzer
  • buildbot (0): automated builds
  • munin (1): ​munin plugins
  • irc (2): IRC bots for #tahoe-lafs channel
  • release (3): related to the release process

Tickets by Milestone

Tickets by Component

See ComponentDefinitions for an explanation of what each component means.

The Standard Trac Tickets Page