naming conventions (and an intro)

[Kyle VanderBeek]

I couldn't find a naming convention set in the wiki, so I'll ask here.  
As I prep the bits and pieces for packaged pylons on Fedora, I'm seeing 
a lot of varied package names and project names.  Projects like Pylons 
and Mako refer to themselves with caps, but provide PEP-8 friendly 
lowercase package names, and I'm wondering how we should map these to 
package names.

Personally I'd rather not see a package named "Mako" since it is 
meaningless outside the context of python and provides nothing in 
/usr/bin.  I'd probably name the package python-mako to make it sort 
near python-*, which seems to be fairly common in Fedora and RedHat.  
Does that sound right to you all?

By the way, I'm Kyle VanderBeek, professional software developer for
IronPort (a Cisco Company).  I've been doing software development for
more than a decade now, as well as administering a variety of Unix
systems including RedHat/RPM Linux distros going back to 4.0 (no, not 
RHEL 4; actual RedHat Linux 4.0).  I currently do the majority of my 
work in Python, writing massive email anti-spam and reputation systems 
to protect your mom's Inbox.

-- 
kylev at kylev.com
  Some people have a way with words, while others... erm... thingy.