[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:  closed
     Priority:  normal     |  Milestone:  2.0.0
    Component:  packaging  |    Version:  1.9.2
   Resolution:  wontfix    |   Keywords:  cleanup
Launchpad Bug:             |
---------------------------+---------------------
Changes (by exarkun):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 Most recent discussion I've heard in the vicinity of this idea is that
 instead of simply renaming the package containing the current Python
 codebase, a new Python package should be started with exposes a more
 coherent, publicly supported Python API (presumably entirely or primarily
 on top of the current Python API, all of which is generally considered
 internal).  This would argue against the renaming described here,
 particularly any renaming to a desirable name which could be used for the
 package with a publicly supported Python API (where the name is a lot more
 valuable).

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