stale doc files #421
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#421
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I've been noticing stale doc files or wiki pages. Here is a partial list. I'd like to go through these and either delete them, update them, or replace them with a reference to the new replacement doc.
I will remove the first four docs (FileEncoding, ShareEncoding, PeerSelection, and ChangingFilesWhileCopyingThem) from the wiki pages, and put their contents (whatever remains accurate and relevant) into the source tree in source:docs
We're going to try to put long-term docs in the source tree, and use the mailing list for discussions (rather than using wiki pages for discussions).
docs/install-details.html and README.w32 are now covered by #194, and are removed from this ticket.
I will make sure there is a ticket present for everything in roadmap.txt, and then delete roadmap.txt
Hm, it's actually kind of nice to have the HTML docs for this stuff, because
then the pictures and the text are on the same page.
Having the docs in source:docs/ makes them more likely to be updated, though.
I'll start by updating the docs in the wiki.
What needs updating:
key is computed with a convergence secret, and we use SHA-256d. The
encryption key can also be random instead of using CHK. The "verifierid"
is actually the flat ciphertext hash, which is a small (and optional)
component of the UEB block. Encoding and share merkle trees work as
described.
page, and should be moved to the [Bibliography]Bibliography
page that it points to needs small updates (but should be moved to
source:docs/): replace "verifierid" with "storage index".
discussion. I'll turn this into a ticket.
file then removed from the source tree
ShareEncoding: removed
ChangingFilesWhileCopyingThem: turned into ticket #427
PeerSelection: actually, this could be useful from a historical perspective: it explains paths we didn't go down. Should such things be put into source:docs ? Or on a wiki page?
ok, PeerSelection is gone, and moved into the source tree in source:docs/historical/
and FileEncoding is gone. The only thing left to this ticket is roadmap.txt .
..and roadmap.txt is gone, split into a bunch of separate tickets (mostly in the #444 to #451 range). This ticket is now done.