Refine use case documentation for non-technical audiences. #787
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
3 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#787
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?
Some use cases for Tahoe-LAFS would appeal to enterprise architects, CIOs, and other roles with less technical savvy.
This ticket is fulfilled when there's a slick document that contrasts an enterprise use case with similar competing technologies.
An example consideration for the intended audience is PCI DSS compliance, a standard many security officers must addrress. A document describing what challenges a deployment of Tahoe-LAFS would face for PCI auditing would lower barriers to adoption for many online business applications.
http://en.wikipedia.org/wiki/PCI_DSS
See also an example criticism of ec2+s3 to understand the target audience:
http://www.mckeay.net/2009/08/14/cannot-achieve-pci-compliance-with-amazon-ec2s3/
What would it take to close this ticket? I think it is too general to close -- the docs will always need to be improved for various audience. How about if we replace this ticket with "Write a document describing Tahoe-LAFS for PCI DSS compliance purposes"? Is that a reasonable task to set for ourselves?
If none of existing satisfies your needs, you can add it to UseCases page and link to this issue to allow other interested parties to ellaborate and contribute.