[Top][All Lists]

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

Re: [Savannah-hackers] Re: [Savannah] set1 want to be a GNU package

From: Mathieu Roy
Subject: Re: [Savannah-hackers] Re: [Savannah] set1 want to be a GNU package
Date: Wed, 24 Jul 2002 08:32:32 +0200

Le mar 23 jui 2002 à  3h02, Free Software Foundation a écrit :
[ Sorry for the late reply to this email.  This address frequently
  backlogged, and we are always struggling to catch up. ]

Currently, on the official savannah site, we are only permitting
that are officially GNU software.  (We are beginning to add
this so that any GPL-compatible software can be hosted, but that is
completely done yet.)

Actually, now (2002/07/24), any GPL-compatible software can be hosted on savannah

We can certainly evaluate your software to see if it can officially
GNU software.

To make your program into official GNU software
(, you will
first need to agree to follow GNU policies.  This is somewhat
because each maintainer of an official GNU package agrees to stand
with the
GNU project on important matters of software freedom.

I have included a brief summary of the major policies with this
For a more detailed description, please read the GNU Maintainers Guide
( in detail before you

If you are agreeable to these policies, the next step is for the
to be evaluated for inclusion in GNU.  To do this, I need the
things in a self-contained email:

   * A short (paragraph or so) description of the program.
   * A URL where the source code can be downloaded.

(I realize that you may have given me all that information already in
 previous messages, but to get the process moving, please send it
again in
 a self-contained email so that I can easily pass it on to our

One thing that you should also address in your submission is how you
this integrating with GNU Hurd later on.

address@hidden <address@hidden> wrote:
> Submitter: <address@hidden>
> Project Full Name:  Set/1
> Project System Name:  set1
> License:  gpl
> Approval URL:

> Description: The purpose of this project is to provide an entirely
> object-oriented, platform- and machine-independant L4 and/or Mach
> microkernel and set of servers which is written completely in C++.
> microkernel will provide machine- and platform-independence via
> templatized generic classes and objects, and the servers will be
> completely message-based via Objective-C-like message semantics.

Bradley M. Kuhn, Executive Director
Free Software Foundation     |  Phone: +1-617-542-5942
59 Temple Place, Suite 330   |  Fax:   +1-617-542-2652
Boston, MA 02111-1307  USA   |  Web:

Here's the explanation of what it means for a program to be a GNU

Calling a program GNU software means that its developers and the GNU
project agree that "This program is part of the GNU project, released
under the aegis of GNU"--and say so in the program.

This means that we normally put the program on (although
we could instead refer to the developer's choice of ftp site).

This means that we put the official pages describing the program on
the, specifically in /software/PROGRAMNAME.  Whenever you
give out the URL for the package home page, you would give this
address.  (It is ok to put more informal pages about secondary issues,
such as discussion meant for people who want to help develop the
package, and pages that access data bases, on some other site.)

It means that the developers agree to pay some attention to making the
program work well with the rest of the GNU system--and conversely that
the GNU project will encourage other GNU maintainers to pay some
attention to making their programs fit in well with it.

Just what it means to make programs work well together is mainly a
practical matter that depends on what the program does.  But there are
a few general principles.  Certain parts of the GNU coding standards
directly affect the consistency of the whole system.  These include
the standards for configuring and building a program, and the
standards for command-line options.  It is important to make all GNU
programs follow these standards, where they are applicable.

Another important GNU standard is that GNU programs should come with
documentation in Texinfo format.  That is the GNU standard
format, and it can be converted automatically into various other
You can use DocBook format or another suitable format for the
sources, as long as you verify that converting it automatically into
Texinfo gives correct and reasonable results.

If a GNU program wants to be extensible, it should use GUILE
( as the programming
language for extensibility--that is the GNU standard extensibility
package.  If the program doesn't use GUILE today, at least there
should be a firm plan to support it in the future.

A GNU program should use the latest version of a license that the GNU
Project recommends--not just any free software license.

A GNU program should not recommend use of any non-free program, and it
should not refer the user to any non-free documentation for free
software.  The need for free documentation to go with free software is
now a major focus of the GNU project; to show that we are serious
about the need for free documentation, we must not contradict our
position by recommending use of documentation that isn't free.

Occasionally there are issues of terminology which are important for
the success of the GNU project as a whole.  So we expect maintainers
of GNU programs to follow them.  For example, the documentation files
and comments in the program should speak of Linux-based GNU systems or
GNU/Linux systems, rather than calling the whole system "Linux", and
should use the term "free software" rather than "open source".

Deciding that a program is GNU software does not necessarily require
transferring copyright to the FSF; that is a separate question.  If
you transfer the copyright to the FSF, the FSF will enforce the GPL
for the program if someone violates it; if you keep the copyright,
enforcement will be up to you.

Mathieu Roy (GPG Key)

reply via email to

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