[clo-devel] Project proposal (Handling Spam (Was Payment Past Due, account))

[Nikodemus Siivola]

On Mon, Nov 17, 2003 at 08:40:03AM -0800, Miles Egan wrote:

> I wonder if it's really a good thing for clo admins to exercise this
> much control over projects, including their names.  Perhaps it would be
> better to just dispense names on a first come, first serve basis?  I'm
> worried that this will come across as heavy handed.

Ouch. 

Miles, very good point. And somewhat embarassing as I've agitated for
first-come, first-served paradigm myself... ;)

I think that we might add naming guidelines to the FAQ,
along with the note that tey are not compulsory.

Here's a draft:

--snip--
Naming Guidelines

 You're free to name your project almost any way you like. Names are
 given out on "first come, first served" basis.

 Common-lisp.net reserves the right to veto any name, but we really
 don't expect to need to use that right unless there are potential
 legal issues involved. More likely we just tell you if we don't like
 the name, but you're free to use it anyway.

 However, here are some guidelines:

  * Informal namespace sharing with http://www.cliki.net/. If there is
    a Cliki page with the same name as your project name but is not
    related, please reconsider.

  * Bindings to foreign libraries should generally be named "cl-foo", where
    foo is the foreign library's name. Eg. libcurses binding would be
    cl-curses.

  * Common Lisp implemntations of standards or semi-stadard foreign
    libraries should be named "foo", where foo is the common sobriquet
    for the standard.

  * As an alternative to the to above, various puns that insert "l" or
    "cl" somewhere in the name are also popular.

  * In all other cases "namelike" names are preferred. Eg. Osicat, Cells.
--snap--

Comments?

Cheers,

 -- Nikodemus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/clo-devel/attachments/20031118/520625e3/attachment.sig>