Modules created and initial files checked in

[Mike A. Harris]

Daniel Stone wrote:
>>Sure.  What would you suggest as an alternative, ScrnSaver?
> 
> 
> Preferably, yeah.

Why leave out the ee's in "ScreenSaver"?  It's only 2 characters.
I think it'd be nice if there was a template that said something
like:

- modules (must|must not) be in (all uppercase|all lowercase|CamelType)
- modules must not have spaces in their names
- modules (must|must not) have vowels eliminated from their
   names arbitrarily
- modules (must|must not) contain (underscores and/or dashes and/or
   punctuation)
- module names must be chosen that fit within the charset <foo>
- module naming must remain consistent with this set of rules

Not necessarily these exact rules, but just a set of rules that
given a specific module name out loud, anyone could type it
into a commandline without needing to know wether it was uppercase,
lowercase, CamelType, missing vowels (which ones?), etc. and have
a good chance of getting it right from the start.

We've got a chance to create a new era of consistency right now
and I think we should try to develop naming standards for things
to provide future consistency wherever possible.  Granted, for
some things it may not really seem like it should matter, but then
that's why we have the mess of libfoo, libBar, libXbaz, libXBaz,
libXxf86bog, etc. right now.  Look at pkg-config, it's even
worse.  The pkg-config names for tonnes of libraries don't match
the case of the actual library.  Imagine having 3 totally legitimate
libraries spring into existance, all must-haves, named:

libxfoo -> pkg-config name foo
libXFoo -> pkg-config name Xfoo
libxFoo -> pkg-config name xfoo

And the fun when an incompatible libXfoo.so.2 needs to be
simultaneously installed, and ends up being pkg-name Xfoo2.

Granted, there aren't any actual examples I'm personally aware
of right now, but I wouldn't be surprised if there are namespace
collisions.  There are definitely inconsistencies for sure, and
if you know you're using libABC, it's kindof intuitive to assume
the pkgconfig file would be named ABC.pc to match it, so you don't
have to guess, etc...

The same consistency principle holds true for a lot of things,
so it would be really great for the future if we can iron out
all these sort of minor details during this major transitionary
release bump, to see us into the next decade.  ;)