Edgewall Software

Changes between Version 7 and Version 8 of NameSuggestions


Ignore:
Timestamp:
Aug 26, 2006, 1:51:23 AM (18 years ago)
Author:
cmlenz
Comment:

Added name constraints

Legend:

Unmodified
Added
Removed
Modified
  • NameSuggestions

    v7 v8  
    44
    55This page should serve to collect the various name suggestions.
     6
     7Please note that there are several aspects to the project name:
     8 * The project name as used in the logo, website and when referring to the project in general.
     9 * The name of the python package.
     10 * The names of distributed files and the distutils/setuptools project name (as used for PyPI and Python eggs).
     11
     12Both package names and file names impose constraints on the set of potential candidates for a renaming: for example, neither support non-alphanumeric characters, or at least not in a portable manner.
    613
    714== “pyMarkup” ==
     
    1623> hits so far...).
    1724
    18 In response to:
    19 >Response by [http://www.cmlenz.net/ Christopher Lenz]:
    20 >
     25In response to Christian Boos:
     26> Response by [http://www.cmlenz.net/ Christopher Lenz]:
    2127>> I'm not a fan of such prefixed names (!WinFoo, KFoo, GFoo, iFoo, etc).   
    2228>> IMHO those fall in the "cheesy" category ;-)
    2329>> Exceptions are bindings or Python versions of some product, but   
    2430>> otherwise I think it's rather ugly.
    25 Yes, ''pySomething'' usually stands for the Python bindings for that ''Something''.
    26 In the context of Markup, it was more meant to be reminiscent of the `py:` prefix we use everywhere in our templates.
    27 So maybe... py:markup? Additionally, this goes well with the encapsulation in <...> illustrated in the logo.
     31> Yes, ''pySomething'' usually stands for the Python bindings for that ''Something''.
     32> In the context of Markup, it was more meant to be reminiscent of the `py:` prefix we use everywhere in our templates.
     33> So maybe... py:markup? Additionally, this goes well with the encapsulation in <...> illustrated in the logo.
     34
     35See the comment I added at the top of the page about constraints on the project name. I actually like `py:markup`, but don't see how that would work as a name.
    2836
    2937== “Markhor” ==