savannah-register-public
[Top][All Lists]
Advanced

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

[Savannah-register-public] [task #5482] Submission of Open Source X


From: Steven Robson
Subject: [Savannah-register-public] [task #5482] Submission of Open Source X
Date: Sun, 23 Apr 2006 22:33:46 +0000
User-agent: Mozilla/5.0 (compatible; Konqueror/3.5) KHTML/3.5.2 (like Gecko)

Update of task #5482 (project administration):

                  Status:                    None => Cancelled              
             Assigned to:                    None => stevenr                
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #1:

Hi,

I'm evaluating the project you submitted for approval in Savannah.

Savannah's mission is to host free software projects, and we want the public
to think of them as free software projects.  A project name that says "open"
will tend to lead people to think of the project as "open source" instead of
"free software".

We are careful about ethical issues and insist on producing software that is
not dependent on proprietary software.

While Open Source as defined by its founders means something pretty close to
Free Software, it's frequently misunderstood.  For more information, please
see http://www.gnu.org/philosophy/free-software-for-freedom.html.

We would be glad if you accept to use "free" instead of "open" in your
project name.


Additionally, in order to release your project properly and unambiguously
under the GNU GPL, please place copyright notices and permission-to-copy
statements at the beginning of every copyrightable file, usually any file
more than 10 lines long.

In addition, if you haven't already, please include a copy of the plain text
version of the GPL, available from http://www.gnu.org/licenses/gpl.txt, into
a file named "COPYING".

For more information, see http://www.gnu.org/licenses/gpl-howto.html.

If some of your files cannot carry such notices (e.g. binary files), then you
can add a README file in the same directory containing the copyright and
license notices. Check
http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html for further
information.

The GPL FAQ explains why these procedures must be followed.  To learn why a
copy of the GPL must be included with every copy of the code, for example,
see http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude.


Please register your project once more with the changes mentioned above.

Make sure to apply all changes requested, so you will only need to
re-register once.

The re-registration URL found in our acknowledgment of your earlier
registration will direct you to the proper location where you can re-register
your project.

Regards.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/task/?func=detailitem&item_id=5482>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/





reply via email to

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