[tahoe-lafs-trac-stream] [tahoe-lafs] #1950: allmydataectomy: rename "allmydata" package to "tahoe_lafs" or "tahoelafs"

[tahoe-lafs]

#1950: allmydataectomy: rename "allmydata" package to "tahoe_lafs" or "tahoelafs"
---------------------------+-----------------------
     Reporter:  warner     |      Owner:
         Type:  task       |     Status:  new
     Priority:  normal     |  Milestone:  undecided
    Component:  packaging  |    Version:  1.9.2
   Resolution:             |   Keywords:  cleanup
Launchpad Bug:             |
---------------------------+-----------------------

Comment (by nejucomo):

 FWIW my preferences for names are the following from most preferred to
 least:

 1. distribution {{{lafs}}}, python module {{{lafs}}}
 1. distribution {{{tahoelafs}}}, python module {{{tahoelafs}}}  (I prefer
 {{{tahoe-lafs}}} but I prefer consistency more.)
 1. distribution {{{tahoe-lafs}}}, python module {{{tahoelafs}}}
 1. distribution {{{tahoe-lafs}}}, python module {{{tahoe_lafs}}}
 1. other stuff...

 I prefer the name "lafs" without "tahoe" because:

 * It is concise.
 * Every word in the acronym is relevant to its purpose and use, whereas
 "tahoe" is only related to the history.  (How many times have you heard
 "why `tahoe'?")
 * It is relatively available:
  * There is no {{{lafs}}} package in pypi.
  * There is no {{{lafs}}} package in debian 6.
  * There is no {{{lafs}}} package in Ubuntu:
 http://packages.ubuntu.com/search?keywords=lafs&searchon=names&suite=raring&section=all
  * {{{lafs.org}}} is a domain squatter, so presumably that domain could be
 purchased, and has few pre-existing associations / dead links.  See:
 http://lafs.org
  * {{{lafs.net}}} is a legitimate organization unrelated to computing.
 See: http://lafs.net
 * The acronym is the name of a filesystem.  Short filesystem names are
 sexier.

 Two drawbacks:

 * The name "tahoe-lafs" is in widespread use.  If we changed that, there'd
 be a near infinite amount of legacy reference tweaking.  ie: "The lafs
 project (which used to be called tahoe-lafs) ..."
 * The strangeness/uniqueness/unwieldiness of "tahoe" makes it more
 memorable.
 * Changing the name (as daira points out) is busy work.

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