[Top][All Lists]

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

Re: [Savannah-register-public] [task #13713] Submission of Gnu Slip

From: Arthur Schwarz
Subject: Re: [Savannah-register-public] [task #13713] Submission of Gnu Slip
Date: Tue, 11 Aug 2015 16:25:07 -0700

Hi Assaf;

Well(ll), the Gnu eval team has requested a name change and they agreed to
gSlip, standing for Gnu Slip. This is the name which I (thought) I used when
I registered the package with Savannah. I think that you are saying that the
name was somehow changed to Slip. Is this correct?

I have no difficulty with renaming it (again) but I need to know how this
affects current agreements. As a separate issue, a name change will probably
require that existing documentation change to support the new name. I will
have to look into this, and although not opposed to it in theory, I begrudge
the time spent.

In summary, libslip is fine. My concerns are listed above.

I will look at the rest of your comments (thanks) later today or tomorrow.
My intent is to assign all the products to the FSF. Thanks for pointing out
my 'Failure to Communicate'. I will make all changes soon. How I proceed
afterwards, viz, Savannah. I have signed documents turning over my copyright
to the FSF and I intend to make all changes so that that assignment is valid
for all the code.


-----Original Message-----
From: Assaf Gordon [mailto:address@hidden 
Sent: Tuesday, August 11, 2015 4:12 PM
To: Assaf Gordon; Art Schwarz; address@hidden
Subject: [task #13713] Submission of Gnu Slip

Update of task #13713 (project administration):

                  Status:                    None => Wait reply             
             Assigned to:                    None => agn                    


Follow-up Comment #1:

Hello Arthur,

Thank you submitting a new GNU project.

Before creating the project, I do have one suggestion:
The name "slip" is already used by several other technical terms
(e.g. Serial-Line-IP).
Since your project is a library, and the main output is 'libslip.a',
would you be open to calling the project 'libslip' ?
That would hopefully prevent future confusion.


below are few optional items relevant to project hosted on Savannah:

1. Few files don't have any copyright or license statements:
Please consider adding a copyright statement and license notice to these

2. Several files give copyright assignment to "Free Software Foundation"
(e.g. README, NEWS), but the rest of the files are "Copyright (C) 2014
I. Schwarz".

A GNU Package does not automatically assigns copyright to the FSF.
The GNU Maintainer's guide explains:
"GNU packages need not be FSF-copyrighted;
this is up to the author(s), generally at the time the
package is dubbed GNU. When copyright is assigned to the
FSF, the FSF can act to stop GPL violations about the package.
Otherwise, legal actions are up to the author(s)."

If you do want to re-assign copyright, then you'll need to contact the FSF
and explicitly assign it.
And then - *all* source code must be "copyright (C) free software
instead of "Arthur I. Scharz".

If you choose not to assign copyright to FSF, please update the README/NEWS
(and any
other file you've created) to list you as the copyright owner.

3. There is a large user-manual in PDF format,
but without the source code (needed to re-generate this PDF).
It is recommended to provide a source code in texinfo format,
see here:

And few minor recommendations:

4. seems like there's a superfluous 'auto' in line 28 of ''.

5. The code in its current form doesn't compile for me,
file 'src/' includes a non-existing file 'lex.slip.h' - 
there is a file named 'lex.Slip.h' (with a capital 'S') - perhaps that's a
It's probably best to avoid files with mixed-case for portability.

6. The unit-test program is called 'test' (in - on unix systems
there is a common program
called 'test' (and usually also a shell builtin called 'test') - this might
cause some issues.
it's probably safer to rename it for portability.

 - assaf


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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