make the wui show the underlying LAFS model -- one WUI page per link in LAFS #277

Open
opened 2008-01-15 21:56:39 +00:00 by zooko · 5 comments

If you are looking at a directory and you want to get a read-only link to a child of it, currently you have to get the read-only URI and then prepend that with <http://127.0.0.1:8123/uri/>. It would be nice if there were a "read-only-link" hyperlink next to the "URI-link" hyperlink. But for that matter, maybe the time has come to make all representations of caps emitted by tahoe start with <http://127.0.0.1:8123/uri/>. Then we could simplify the wui to offer the hyperlink to the file and a read-only hyperlink (if and only if you have write access to the file). We could remove or move into a special metadata-page the JSON and text-plain links, and remove entirely the URI and readonly-URI links, the URI link for files, which is identical to the actual hyperlink to the file, and the text-plain link.

If we implement #103 -- "navigate by URIs in webish.py" -- then we can remove the URI link for files, too.

Therefore, we can have a nice simple wui with at most two hyperlinks per child: the read-write link (if appropriate) and the read-only link (if appropriate). In addition to those two links, there would be a set of actions (buttons) available, if appropriate: delete, overwrite, rename, check, view metadata.

If you are looking at a directory and you want to get a read-only link to a child of it, currently you have to get the read-only URI and then prepend that with `<http://127.0.0.1:8123/uri/>`. It would be nice if there were a "read-only-link" hyperlink next to the "URI-link" hyperlink. But for that matter, maybe the time has come to make all representations of caps emitted by tahoe start with `<http://127.0.0.1:8123/uri/>`. Then we could simplify the wui to offer the hyperlink to the file and a `read-only` hyperlink (if and only if you have write access to the file). We could remove or move into a special metadata-page the `JSON` and `text-plain` links, and remove entirely the `URI` and `readonly-URI` links, the `URI` link for files, which is identical to the actual hyperlink to the file, and the `text-plain` link. If we implement #103 -- "navigate by URIs in webish.py" -- then we can remove the `URI` link for files, too. Therefore, we can have a nice simple wui with at most two hyperlinks per child: the read-write link (if appropriate) and the read-only link (if appropriate). In addition to those two links, there would be a set of actions (buttons) available, if appropriate: delete, overwrite, rename, check, view metadata.
zooko added the
c/code-frontend-web
p/major
t/enhancement
v/0.7.0
labels 2008-01-15 21:56:39 +00:00
zooko added this to the eventually milestone 2008-01-15 21:56:39 +00:00
zooko self-assigned this 2008-01-15 21:56:39 +00:00
Author

Hm.. The more that I think about this, the more I realize that our wui is attempting to simplify something about the underlying model from the user, and that it might be better to make this underlying thing explicit in the wui.

This underlying fact is that files are standalone objects which have a contents and a size but not a name or any other metadata, and that the entries in directories are links to files, with metadata associated with the link but not with the file.

Make sense?

So for example, you can have two different directories that contain the same child, and it really is the same file -- for example if it is a mutable file (or a directory), and it gets change, then the change will appear in it regardless of which parent directory was used to get to it.

So a way that the wui could be refactored to follow the underlying model more closely would be for the web page representing a directory to contain buttons only for the actions that effect a link: delete (which should be renamed "unlink" in the wui), rename, follow (i.e. a hyperlink to the wui page child), and examine and change the metadata. Then there could be a per-file page which contains the operations that you can do to a file: view its contents (a hyperlink to the actual contents), view its contents read-only (a read-only hyperlink to the actual contents), view its size, check its health, and overwrite it.

But this would make the normal task of navigating from a directory listing to the file contents into a two-click operation instead of one-click. Also is would make all other operations on files, such as checking their status, into two-click operations. Relatedly, suppose that there is an HTML file which contains a hyperlink to another file which is stored in Tahoe, and you click that hyperlink. Currently, the wui will serve up the file contents to you (which is good), but it doesn't make available the controls that you can do to that file: check its health and overwrite it.

Currently there is no way to give someone access to a mutable file so that they will be able to change it without also giving them access to some parent directory which points to the file. They don't actually require access to any parent directory in order to change the contents of the file or to check its health, but the wui has no way to give them those controls other than by showing them a parent directory.

So perhaps the best wui would have a small bit of HTML which would be visible in a frame at the top of a file when the file is viewed directly, and then the directory page can have just links directly to files. :-)

Hm.. The more that I think about this, the more I realize that our wui is attempting to simplify something about the underlying model from the user, and that it might be better to make this underlying thing explicit in the wui. This underlying fact is that files are standalone objects which have a contents and a size but not a name or any other metadata, and that the entries in directories are links to files, with metadata associated with the link but not with the file. Make sense? So for example, you can have two different directories that contain the same child, and it really is the same file -- for example if it is a mutable file (or a directory), and it gets change, then the change will appear in it regardless of which parent directory was used to get to it. So a way that the wui could be refactored to follow the underlying model more closely would be for the web page representing a directory to contain buttons only for the actions that effect a link: delete (which should be renamed "unlink" in the wui), rename, follow (i.e. a hyperlink to the wui page child), and examine and change the metadata. Then there could be a per-*file* page which contains the operations that you can do to a file: view its contents (a hyperlink to the actual contents), view its contents read-only (a read-only hyperlink to the actual contents), view its size, check its health, and overwrite it. But this would make the normal task of navigating from a directory listing to the file contents into a two-click operation instead of one-click. Also is would make all other operations on files, such as checking their status, into two-click operations. Relatedly, suppose that there is an HTML file which contains a hyperlink to another file which is stored in Tahoe, and you click that hyperlink. Currently, the wui will serve up the file contents to you (which is good), but it doesn't make available the controls that you can do to that file: check its health and overwrite it. Currently there is no way to give someone access to a mutable file so that they will be able to change it without also giving them access to some parent directory which points to the file. They don't actually require access to any parent directory in order to change the contents of the file or to check its health, but the wui has no way to give them those controls other than by showing them a parent directory. So perhaps the best wui would have a small bit of HTML which would be visible in a frame at the top of a file when the file is viewed directly, and then the directory page can have just links directly to files. :-)
zooko changed title from simplify the wui to simplify the wui; make the wui show the underlying tahoe filesystem model 2008-01-18 22:16:26 +00:00
Author

Oh, but this header frame must be absent on a normal HTTP GET -- HTTP GET is the way to get the actual data. So we need some nice RESTful way to indicate whether the wui/wapi server should just give me the data or give me a control panel for the file as well as the data itself in a separate frame.

Furthermore, if someone gives me a hyperlink which would yield just the data of the file, I want to be able to somehow easily navigate to the control panel for that file

I suspect that the RESTful (and the object-capability/WebKEYful) way to do this is for the control panel to be a separate resource from the file itself. I suppose <http://127.0.0.1:8123/view/$CAP> could return the page with both the control pane and the file contents pane, where <http://127.0.0.1:8123/data/$CAP> could return just the file contents.

Oh, but this header frame must be absent on a normal HTTP GET -- HTTP GET is the way to get the actual data. So we need some nice RESTful way to indicate whether the wui/wapi server should just give me the data or give me a control panel for the file as well as the data itself in a separate frame. Furthermore, if someone gives me a hyperlink which would yield just the data of the file, I want to be able to somehow easily navigate to the control panel for that file I suspect that the RESTful (and the object-capability/WebKEYful) way to do this is for the control panel to be a separate resource from the file itself. I suppose `<http://127.0.0.1:8123/view/$CAP>` could return the page with both the control pane and the file contents pane, where `<http://127.0.0.1:8123/data/$CAP>` could return just the file contents.
Author

See also #418 (URI scheme), #221 (give proper filenames on download), #217 (DSA-based mutable files -- small URLs, fast file creation), #102 (smaller and prettier directory URIs), and #103 (navigate by URIs in webish.py)

See also #418 (URI scheme), #221 (give proper filenames on download), #217 (DSA-based mutable files -- small URLs, fast file creation), #102 (smaller and prettier directory URIs), and #103 (navigate by URIs in webish.py)

in the current code, this "control panel" is obtained by appending "?t=info" to the /uri/$CAP URL. The t=info page contains read-only links, storage index strings, any other data we can extract from the URI, and buttons to perform check/verify/repair. The t=info page for a directory also contains buttons to start deep-check/build-manifest/deep-stats operations.

The webapi has changed a bit since this ticket was first created. Mutable files can be accessed without going through a directory: /uri/URI:SSK:... allows GET and PUT, as well as POST with a variety of ?t= suffixes (for the benefit of HTML forms).

I wouldn't object to a parallel namespace for getting at this metadata/control-panel. Perhaps /info/$CAP ?

in the current code, this "control panel" is obtained by appending "?t=info" to the /uri/$CAP URL. The t=info page contains read-only links, storage index strings, any other data we can extract from the URI, and buttons to perform check/verify/repair. The t=info page for a directory also contains buttons to start deep-check/build-manifest/deep-stats operations. The webapi has changed a bit since this ticket was first created. Mutable files can be accessed without going through a directory: `/uri/URI:SSK:...` allows GET and PUT, as well as POST with a variety of ?t= suffixes (for the benefit of HTML forms). I wouldn't object to a parallel namespace for getting at this metadata/control-panel. Perhaps /info/$CAP ?
zooko changed title from simplify the wui; make the wui show the underlying tahoe filesystem model to make the wui show the underlying LAFS model -- one WUI page per link in LAFS 2012-08-27 18:39:41 +00:00
Author

#1499 is related to this, possibly a special case of this.

#1499 is related to this, possibly a special case of this.
Sign in to join this conversation.
No labels
c/code
c/code-dirnodes
c/code-encoding
c/code-frontend
c/code-frontend-cli
c/code-frontend-ftp-sftp
c/code-frontend-magic-folder
c/code-frontend-web
c/code-mutable
c/code-network
c/code-nodeadmin
c/code-peerselection
c/code-storage
c/contrib
c/dev-infrastructure
c/docs
c/operational
c/packaging
c/unknown
c/website
kw:2pc
kw:410
kw:9p
kw:ActivePerl
kw:AttributeError
kw:DataUnavailable
kw:DeadReferenceError
kw:DoS
kw:FileZilla
kw:GetLastError
kw:IFinishableConsumer
kw:K
kw:LeastAuthority
kw:Makefile
kw:RIStorageServer
kw:StringIO
kw:UncoordinatedWriteError
kw:about
kw:access
kw:access-control
kw:accessibility
kw:accounting
kw:accounting-crawler
kw:add-only
kw:aes
kw:aesthetics
kw:alias
kw:aliases
kw:aliens
kw:allmydata
kw:amazon
kw:ambient
kw:annotations
kw:anonymity
kw:anonymous
kw:anti-censorship
kw:api_auth_token
kw:appearance
kw:appname
kw:apport
kw:archive
kw:archlinux
kw:argparse
kw:arm
kw:assertion
kw:attachment
kw:auth
kw:authentication
kw:automation
kw:avahi
kw:availability
kw:aws
kw:azure
kw:backend
kw:backoff
kw:backup
kw:backupdb
kw:backward-compatibility
kw:bandwidth
kw:basedir
kw:bayes
kw:bbfreeze
kw:beta
kw:binaries
kw:binutils
kw:bitcoin
kw:bitrot
kw:blacklist
kw:blocker
kw:blocks-cloud-deployment
kw:blocks-cloud-merge
kw:blocks-magic-folder-merge
kw:blocks-merge
kw:blocks-raic
kw:blocks-release
kw:blog
kw:bom
kw:bonjour
kw:branch
kw:branding
kw:breadcrumbs
kw:brians-opinion-needed
kw:browser
kw:bsd
kw:build
kw:build-helpers
kw:buildbot
kw:builders
kw:buildslave
kw:buildslaves
kw:cache
kw:cap
kw:capleak
kw:captcha
kw:cast
kw:centos
kw:cffi
kw:chacha
kw:charset
kw:check
kw:checker
kw:chroot
kw:ci
kw:clean
kw:cleanup
kw:cli
kw:cloud
kw:cloud-backend
kw:cmdline
kw:code
kw:code-checks
kw:coding-standards
kw:coding-tools
kw:coding_tools
kw:collection
kw:compatibility
kw:completion
kw:compression
kw:confidentiality
kw:config
kw:configuration
kw:configuration.txt
kw:conflict
kw:connection
kw:connectivity
kw:consistency
kw:content
kw:control
kw:control.furl
kw:convergence
kw:coordination
kw:copyright
kw:corruption
kw:cors
kw:cost
kw:coverage
kw:coveralls
kw:coveralls.io
kw:cpu-watcher
kw:cpyext
kw:crash
kw:crawler
kw:crawlers
kw:create-container
kw:cruft
kw:crypto
kw:cryptography
kw:cryptography-lib
kw:cryptopp
kw:csp
kw:curl
kw:cutoff-date
kw:cycle
kw:cygwin
kw:d3
kw:daemon
kw:darcs
kw:darcsver
kw:database
kw:dataloss
kw:db
kw:dead-code
kw:deb
kw:debian
kw:debug
kw:deep-check
kw:defaults
kw:deferred
kw:delete
kw:deletion
kw:denial-of-service
kw:dependency
kw:deployment
kw:deprecation
kw:desert-island
kw:desert-island-build
kw:design
kw:design-review-needed
kw:detection
kw:dev-infrastructure
kw:devpay
kw:directory
kw:directory-page
kw:dirnode
kw:dirnodes
kw:disconnect
kw:discovery
kw:disk
kw:disk-backend
kw:distribute
kw:distutils
kw:dns
kw:do_http
kw:doc-needed
kw:docker
kw:docs
kw:docs-needed
kw:dokan
kw:dos
kw:download
kw:downloader
kw:dragonfly
kw:drop-upload
kw:duplicity
kw:dusty
kw:earth-dragon
kw:easy
kw:ec2
kw:ecdsa
kw:ed25519
kw:egg-needed
kw:eggs
kw:eliot
kw:email
kw:empty
kw:encoding
kw:endpoint
kw:enterprise
kw:enum34
kw:environment
kw:erasure
kw:erasure-coding
kw:error
kw:escaping
kw:etag
kw:etch
kw:evangelism
kw:eventual
kw:example
kw:excess-authority
kw:exec
kw:exocet
kw:expiration
kw:extensibility
kw:extension
kw:failure
kw:fedora
kw:ffp
kw:fhs
kw:figleaf
kw:file
kw:file-descriptor
kw:filename
kw:filesystem
kw:fileutil
kw:fips
kw:firewall
kw:first
kw:floatingpoint
kw:flog
kw:foolscap
kw:forward-compatibility
kw:forward-secrecy
kw:forwarding
kw:free
kw:freebsd
kw:frontend
kw:fsevents
kw:ftp
kw:ftpd
kw:full
kw:furl
kw:fuse
kw:garbage
kw:garbage-collection
kw:gateway
kw:gatherer
kw:gc
kw:gcc
kw:gentoo
kw:get
kw:git
kw:git-annex
kw:github
kw:glacier
kw:globalcaps
kw:glossary
kw:google-cloud-storage
kw:google-drive-backend
kw:gossip
kw:governance
kw:grid
kw:grid-manager
kw:gridid
kw:gridsync
kw:grsec
kw:gsoc
kw:gvfs
kw:hackfest
kw:hacktahoe
kw:hang
kw:hardlink
kw:heartbleed
kw:heisenbug
kw:help
kw:helper
kw:hint
kw:hooks
kw:how
kw:how-to
kw:howto
kw:hp
kw:hp-cloud
kw:html
kw:http
kw:https
kw:i18n
kw:i2p
kw:i2p-collab
kw:illustration
kw:image
kw:immutable
kw:impressions
kw:incentives
kw:incident
kw:init
kw:inlineCallbacks
kw:inotify
kw:install
kw:installer
kw:integration
kw:integration-test
kw:integrity
kw:interactive
kw:interface
kw:interfaces
kw:interoperability
kw:interstellar-exploration
kw:introducer
kw:introduction
kw:iphone
kw:ipkg
kw:iputil
kw:ipv6
kw:irc
kw:jail
kw:javascript
kw:joke
kw:jquery
kw:json
kw:jsui
kw:junk
kw:key-value-store
kw:kfreebsd
kw:known-issue
kw:konqueror
kw:kpreid
kw:kvm
kw:l10n
kw:lae
kw:large
kw:latency
kw:leak
kw:leasedb
kw:leases
kw:libgmp
kw:license
kw:licenss
kw:linecount
kw:link
kw:linux
kw:lit
kw:localhost
kw:location
kw:locking
kw:logging
kw:logo
kw:loopback
kw:lucid
kw:mac
kw:macintosh
kw:magic-folder
kw:manhole
kw:manifest
kw:manual-test-needed
kw:map
kw:mapupdate
kw:max_space
kw:mdmf
kw:memcheck
kw:memory
kw:memory-leak
kw:mesh
kw:metadata
kw:meter
kw:migration
kw:mime
kw:mingw
kw:minimal
kw:misc
kw:miscapture
kw:mlp
kw:mock
kw:more-info-needed
kw:mountain-lion
kw:move
kw:multi-users
kw:multiple
kw:multiuser-gateway
kw:munin
kw:music
kw:mutability
kw:mutable
kw:mystery
kw:names
kw:naming
kw:nas
kw:navigation
kw:needs-review
kw:needs-spawn
kw:netbsd
kw:network
kw:nevow
kw:new-user
kw:newcaps
kw:news
kw:news-done
kw:news-needed
kw:newsletter
kw:newurls
kw:nfc
kw:nginx
kw:nixos
kw:no-clobber
kw:node
kw:node-url
kw:notification
kw:notifyOnDisconnect
kw:nsa310
kw:nsa320
kw:nsa325
kw:numpy
kw:objects
kw:old
kw:openbsd
kw:openitp-packaging
kw:openssl
kw:openstack
kw:opensuse
kw:operation-helpers
kw:operational
kw:operations
kw:ophandle
kw:ophandles
kw:ops
kw:optimization
kw:optional
kw:options
kw:organization
kw:os
kw:os.abort
kw:ostrom
kw:osx
kw:osxfuse
kw:otf-magic-folder-objective1
kw:otf-magic-folder-objective2
kw:otf-magic-folder-objective3
kw:otf-magic-folder-objective4
kw:otf-magic-folder-objective5
kw:otf-magic-folder-objective6
kw:p2p
kw:packaging
kw:partial
kw:password
kw:path
kw:paths
kw:pause
kw:peer-selection
kw:performance
kw:permalink
kw:permissions
kw:persistence
kw:phone
kw:pickle
kw:pip
kw:pipermail
kw:pkg_resources
kw:placement
kw:planning
kw:policy
kw:port
kw:portability
kw:portal
kw:posthook
kw:pratchett
kw:preformance
kw:preservation
kw:privacy
kw:process
kw:profile
kw:profiling
kw:progress
kw:proxy
kw:publish
kw:pyOpenSSL
kw:pyasn1
kw:pycparser
kw:pycrypto
kw:pycrypto-lib
kw:pycryptopp
kw:pyfilesystem
kw:pyflakes
kw:pylint
kw:pypi
kw:pypy
kw:pysqlite
kw:python
kw:python3
kw:pythonpath
kw:pyutil
kw:pywin32
kw:quickstart
kw:quiet
kw:quotas
kw:quoting
kw:raic
kw:rainhill
kw:random
kw:random-access
kw:range
kw:raspberry-pi
kw:reactor
kw:readonly
kw:rebalancing
kw:recovery
kw:recursive
kw:redhat
kw:redirect
kw:redressing
kw:refactor
kw:referer
kw:referrer
kw:regression
kw:rekey
kw:relay
kw:release
kw:release-blocker
kw:reliability
kw:relnotes
kw:remote
kw:removable
kw:removable-disk
kw:rename
kw:renew
kw:repair
kw:replace
kw:report
kw:repository
kw:research
kw:reserved_space
kw:response-needed
kw:response-time
kw:restore
kw:retrieve
kw:retry
kw:review
kw:review-needed
kw:reviewed
kw:revocation
kw:roadmap
kw:rollback
kw:rpm
kw:rsa
kw:rss
kw:rst
kw:rsync
kw:rusty
kw:s3
kw:s3-backend
kw:s3-frontend
kw:s4
kw:same-origin
kw:sandbox
kw:scalability
kw:scaling
kw:scheduling
kw:schema
kw:scheme
kw:scp
kw:scripts
kw:sdist
kw:sdmf
kw:security
kw:self-contained
kw:server
kw:servermap
kw:servers-of-happiness
kw:service
kw:setup
kw:setup.py
kw:setup_requires
kw:setuptools
kw:setuptools_darcs
kw:sftp
kw:shared
kw:shareset
kw:shell
kw:signals
kw:simultaneous
kw:six
kw:size
kw:slackware
kw:slashes
kw:smb
kw:sneakernet
kw:snowleopard
kw:socket
kw:solaris
kw:space
kw:space-efficiency
kw:spam
kw:spec
kw:speed
kw:sqlite
kw:ssh
kw:ssh-keygen
kw:sshfs
kw:ssl
kw:stability
kw:standards
kw:start
kw:startup
kw:static
kw:static-analysis
kw:statistics
kw:stats
kw:stats_gatherer
kw:status
kw:stdeb
kw:storage
kw:streaming
kw:strports
kw:style
kw:stylesheet
kw:subprocess
kw:sumo
kw:survey
kw:svg
kw:symlink
kw:synchronous
kw:tac
kw:tahoe-*
kw:tahoe-add-alias
kw:tahoe-admin
kw:tahoe-archive
kw:tahoe-backup
kw:tahoe-check
kw:tahoe-cp
kw:tahoe-create-alias
kw:tahoe-create-introducer
kw:tahoe-debug
kw:tahoe-deep-check
kw:tahoe-deepcheck
kw:tahoe-lafs-trac-stream
kw:tahoe-list-aliases
kw:tahoe-ls
kw:tahoe-magic-folder
kw:tahoe-manifest
kw:tahoe-mkdir
kw:tahoe-mount
kw:tahoe-mv
kw:tahoe-put
kw:tahoe-restart
kw:tahoe-rm
kw:tahoe-run
kw:tahoe-start
kw:tahoe-stats
kw:tahoe-unlink
kw:tahoe-webopen
kw:tahoe.css
kw:tahoe_files
kw:tahoewapi
kw:tarball
kw:tarballs
kw:tempfile
kw:templates
kw:terminology
kw:test
kw:test-and-set
kw:test-from-egg
kw:test-needed
kw:testgrid
kw:testing
kw:tests
kw:throttling
kw:ticket999-s3-backend
kw:tiddly
kw:time
kw:timeout
kw:timing
kw:to
kw:to-be-closed-on-2011-08-01
kw:tor
kw:tor-protocol
kw:torsocks
kw:tox
kw:trac
kw:transparency
kw:travis
kw:travis-ci
kw:trial
kw:trickle
kw:trivial
kw:truckee
kw:tub
kw:tub.location
kw:twine
kw:twistd
kw:twistd.log
kw:twisted
kw:twisted-14
kw:twisted-trial
kw:twitter
kw:twn
kw:txaws
kw:type
kw:typeerror
kw:ubuntu
kw:ucwe
kw:ueb
kw:ui
kw:unclean
kw:uncoordinated-writes
kw:undeletable
kw:unfinished-business
kw:unhandled-error
kw:unhappy
kw:unicode
kw:unit
kw:unix
kw:unlink
kw:update
kw:upgrade
kw:upload
kw:upload-helper
kw:uri
kw:url
kw:usability
kw:use-case
kw:utf-8
kw:util
kw:uwsgi
kw:ux
kw:validation
kw:variables
kw:vdrive
kw:verify
kw:verlib
kw:version
kw:versioning
kw:versions
kw:video
kw:virtualbox
kw:virtualenv
kw:vista
kw:visualization
kw:visualizer
kw:vm
kw:volunteergrid2
kw:volunteers
kw:vpn
kw:wapi
kw:warners-opinion-needed
kw:warning
kw:weapi
kw:web
kw:web.port
kw:webapi
kw:webdav
kw:webdrive
kw:webport
kw:websec
kw:website
kw:websocket
kw:welcome
kw:welcome-page
kw:welcomepage
kw:wiki
kw:win32
kw:win64
kw:windows
kw:windows-related
kw:winscp
kw:workaround
kw:world-domination
kw:wrapper
kw:write-enabler
kw:wui
kw:x86
kw:x86-64
kw:xhtml
kw:xml
kw:xss
kw:zbase32
kw:zetuptoolz
kw:zfec
kw:zookos-opinion-needed
kw:zope
kw:zope.interface
p/blocker
p/critical
p/major
p/minor
p/normal
p/supercritical
p/trivial
r/cannot reproduce
r/duplicate
r/fixed
r/invalid
r/somebody else's problem
r/was already fixed
r/wontfix
r/worksforme
t/defect
t/enhancement
t/task
v/0.2.0
v/0.3.0
v/0.4.0
v/0.5.0
v/0.5.1
v/0.6.0
v/0.6.1
v/0.7.0
v/0.8.0
v/0.9.0
v/1.0.0
v/1.1.0
v/1.10.0
v/1.10.1
v/1.10.2
v/1.10a2
v/1.11.0
v/1.12.0
v/1.12.1
v/1.13.0
v/1.14.0
v/1.15.0
v/1.15.1
v/1.2.0
v/1.3.0
v/1.4.1
v/1.5.0
v/1.6.0
v/1.6.1
v/1.7.0
v/1.7.1
v/1.7β
v/1.8.0
v/1.8.1
v/1.8.2
v/1.8.3
v/1.8β
v/1.9.0
v/1.9.0-s3branch
v/1.9.0a1
v/1.9.0a2
v/1.9.0b1
v/1.9.1
v/1.9.2
v/1.9.2a1
v/cloud-branch
v/unknown
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac#277
No description provided.