suggested improvements to quick start instructions #1882
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#1882
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
The quick start instructions are very brief and there's a lot of handwaving. I suggest thinking of practical use cases for Tahoe and changing quick start instructions to walk new users through the process.
For example, current documentation is broken into three parts: quickstart, running, and configuration. There's no clear flow or obvious process for actually using Tahoe. The quickstart page outlines the process of installing Tahoe, but a person following that isn't really starting anything.
The running page references a non-existent test grid. And there's no clear process for how to use Tahoe in any particular way. The page essentially just details how to start it with some handwaving over the components. The configuration page is great for a reference but it doesn't clearly help a new user get started.
I really like documentation this Linux distribution uses to guide new users through the install process (http://www.gentoo.org/doc/en/handbook/handbook-x86.xml). Clicking through the manual you'll notice a clear flow with explicit commands and explanations about what you're doing and why that step is necessary.
Obviously in the case of Tahoe such detail (especially in regards to third party software) isn't necessary. I would suggest detailing the installation process with specific use cases in mind. Quick-start should be "how do I get a simple client running quickly?" and then there would be more detailed chapters for storage nodes, introducer, helpers, and etc. These pages should included necessary configuration settings, including any relevant operating system and/or network configuration that's needed. (ex: What ports do you open in a firewall? A new user doesn't necessarily know which ports are necessary.)
Unfortunately I'm not sure I know enough about Tahoe yet to contribute valuable documentation. I'll keep notes though as I start using it more.
This was a duplicate of #1024. However, the initial post on this ticket has a lot of useful ideas, and I hope people looking at #1024 come and read it! rcarz: if you have some notes from your experiences that you could post, that would be helpful!