Refine use case documentation for non-technical audiences. #787

Open
opened 2009-08-14 18:35:59 +00:00 by nejucomo · 3 comments

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.

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.
nejucomo added the
documentation
major
enhancement
labels 2009-08-14 18:35:59 +00:00
nejucomo added this to the undecided milestone 2009-08-14 18:35:59 +00:00
nejucomo self-assigned this 2009-08-14 18:35:59 +00:00
Author

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/

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?

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?
amontero commented 2013-12-03 17:36:58 +00:00
Owner

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.

If none of existing satisfies your needs, you can add it to [UseCases](wiki/UseCases) page and link to this issue to allow other interested parties to ellaborate and contribute.
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#787
No description provided.