Re: [Savannah-hackers-public] Project names requirements

[Assaf Gordon]

On 08/23/2014 06:02 PM, Karl Berry wrote:
>      I don't know what is the current unofficial policy.  But I would suggest
>      requiring more informative names.
>
> Agreed.  As you know, I feel strongly about names :).

Touché :)

> Can you check around on the wiki and requirements.php and see where we
> need to add info about this?  In the meantime, please go ahead as you
> suggest for the two in question.

In the "requirement" page ( http://savannah.gnu.org/register/requirements.php ) 
there is no mention of project name.

In the Guidelines page ( http://savannah.gnu.org/maintenance/HowToGetYourProjectApprovedQuickly/ ), 
there's only a reference to not using "open" and not using "linux" in the 
project's name.

Perhaps something like this?
====
Index: trunk/sviki/HowToGetYourProjectApprovedQuickly.mdwn
===================================================================
--- trunk/sviki/HowToGetYourProjectApprovedQuickly.mdwn (revision 97)
+++ trunk/sviki/HowToGetYourProjectApprovedQuickly.mdwn (working copy)
@@ -30,6 +30,15 @@
     <http://www.gnu.org/help/evaluation.html>
     for information about that process; it does not happen through
     savannah.
+-   If your project is an extension/plugin to an existing project, choose
+    a name indicating this is a plugin and not the core project itself.
+    If your project provides Emacs Plugin for Package FooBar, name your
+    project "foobar-mode" or "foobar-el", not "foobar".
+    Example: "NetHack-EL" <http://savannah.nongnu.org/projects/nethack-el>
+    is the Nethack mode for Emacs.
+-   Do not use a short cryptic abbreviation for your project name.
+    Example: If your project is the "Foo Bar Network Tools", choose a
+    short/system project name such as "foobar-network-tools", not "fnt".
 
 The review we do can be lengthy and difficult for both the submitter and
 the reviewer. Be sure to follow these steps; if your project doesn't
====