[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Assaf Gordon
Subject: Re: [Savannah-hackers-public] Project names requirements
Date: Sat, 23 Aug 2014 20:22:25 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0

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 ( ) 
there is no mention of project name.

In the Guidelines page ( ), 
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 @@
     for information about that process; it does not happen through
+-   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" <>
+    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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]