[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-register-public] [task #5965] Submission of Efficient Symbolic
[Savannah-register-public] [task #5965] Submission of Efficient Symbolic Tools
Tue, 17 Oct 2006 17:21:39 +0000
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:220.127.116.11) Gecko/20060830 Firefox/18.104.22.168 (Debian-1.5.dfsg+22.214.171.124-1)
Update of task #5965 (project administration):
Status: None => Wait reply
Assigned to: None => sp
Follow-up Comment #1:
I'm evaluating the project you submitted for approval in Savannah. While
doing so I've noticed a few problems which are described below.
First of all, 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
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,
Secondly, you added the license notices, but did not add appropriate
http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html for more
information, and update your files.
Also, the address of the FSF has changed, and is now:
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Please update your license notices.
Please update the copy of the license (usually, the 'COPYING' file) in your
package as well.
Updated versions of the GPL, LGPL and GFDL can also be found at:
You can find some background and a possible migration script at
Additionally, even though your project description states you want to license
EST under the "GNU GPL v2 or later", at least some files are licensed under
the "GNU GPL v2 only". Licensing under the "GNU GPL v2 only" is problematic.
Would you agree to license your project under the "GNU GPL v2 or later"?
The reason for this is that when we publish GPL v3, it will be important for
all GPL-covered programs to advance to GPL v3. If you don't put this in the
files now, the only way to port your program to GPL v3 would be to ask each
and every copyright holder, and that may be very difficult.
We can explain the issue in more detail if you wish. If you have concerns
about "GNU GPL v2 or later", we'd be happy to address them too.
Last but not least, Savannah is a central point for development, distribution
and maintenance of GNU Software.
There is a companion site savannah.nongnu.org where we also host Free
Software projects that are not part of the GNU Project, but run on free
However, we do not allow to host your project on Savannah and
SourceForge at the same time, if Savannah is just a project mirror.
Your project development should happen primarily on Savannah.
How do you plan to use your Savannah account?
If you are willing to make the changes mentioned above, please provide us
with an URL to an updated tarball of your project. Upon review, we will
reconsider your project for inclusion in Savannah.
To help us better keep track of your registration, please use the tracker's
web interface following the link below. Do not reply directly, the
registration process is not driven by e-mail, and we will not receive such
Reply to this item at:
Message sent via/by Savannah
- [Savannah-register-public] [task #5965] Submission of Efficient Symbolic Tools,
Stephan Peijnik <=