[tahoe-lafs-trac-stream] [tahoe-lafs] #2009: One Grid to Rule Them All

[tahoe-lafs]

#2009: One Grid to Rule Them All
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  daira
  nejucomo               |     Status:  new
         Type:  defect   |  Milestone:  undecided
     Priority:  normal   |    Version:  n/a
    Component:  unknown  |   Keywords:  extensability, servers-of-
   Resolution:           |  happiness, location, extensability, newurls
Launchpad Bug:           |
-------------------------+-------------------------------------------------
Description changed by nejucomo:

Old description:

> Introducing a use case and associated ticket keyword: `globalcaps`
>
> This is an enhancement request to fulfill this use case:
>
> A user knows a `$CAP` they want to share with the world, so they tweet
> it, or print it in a book, or otherwise share it across time and space to
> a potentially boundless audience.
>
> Anyone using the right software setup who sees that `$CAP` has a
> reasonable chance to retrieve the contents.
>
> There are many related design issues, as well as existing mailing list
> posts and tickets:
>
> * My call to action: https://tahoe-lafs.org/pipermail/tahoe-
> dev/2013-June/008447.html
> * A request for a specific feature that's complementary: https://tahoe-
> lafs.org/pipermail/tahoe-dev/2013-June/008447.html
> * Many relevant keywords which this issue is tagged with.
>
> This ticket has a scoping problem: when do we close it?  I recommend
> closing it when either of these conditions are met:
>
> * One user emails a $CAP to tahoe-dev and another user successfully
> retrieves it without us sharing any introducer information with a
> checkout from the official `tahoe-lafs` git repository (any branch);
> ''or''
>
> * There is a new separate code base established whose purpose is to
> implement this use case and whose URL is in this ticket.

New description:

 Introducing a use case and associated ticket keyword: `globalcaps`

 This is an enhancement request to fulfill this use case:

 A user knows a `$CAP` they want to share with the world, so they tweet it,
 or print it in a book, or otherwise share it across time and space to a
 potentially boundless audience.

 Anyone using the right software setup who sees that `$CAP` has a
 reasonable chance to retrieve the contents.

 There are many related design issues, as well as existing mailing list
 posts and tickets:

 * My call to action: https://tahoe-lafs.org/pipermail/tahoe-
 dev/2013-June/008447.html
 * A request for a "grid id" feature that's complementary: #403
 * Many relevant keywords which this issue is tagged with.

 This ticket has a scoping problem: when do we close it?  I recommend
 closing it when either of these conditions are met:

 * One user emails a $CAP to tahoe-dev and another user successfully
 retrieves it without us sharing any introducer information with a checkout
 from the official `tahoe-lafs` git repository (any branch); ''or''

 * There is a new separate code base established whose purpose is to
 implement this use case and whose URL is in this ticket.

--

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2009#comment:1>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage