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

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

[task #16584] Submission of StoneValley


From: Ineiev
Subject: [task #16584] Submission of StoneValley
Date: Mon, 21 Oct 2024 12:09:40 -0400 (EDT)

Follow-up Comment #48, task #16584 (group administration):

On Fri, Oct 18, 2024 at 02:58:01PM -0400, John Cage wrote:
> > Could you please check the GPL HowTo once again?
> > https://www.gnu.org/licenses/gpl-howto.html
> 
> Now I got it, I need to add both LGPL and GPL license to my project, because
> in the above file, there are:
>     *) Add a COPYING file with a copy of the GNU GPL or GNU AGPL.
>     *) Also add a COPYING.LESSER file with a copy of the GNU LGPL, if you
use
> that.
>     *) Put a license notice in each file.
> 
> 
> > I see; we agreed that such approach was wrong by comment #35; however,
> > you didn't think that the tarball needed updating, did you?
> 
> I am sorry, no, I did't update the tarball. I would update it again in this
> comment.

Thank you!  Now you should learn to specify the licensing terms of your
package consistently.  In the current tarball, one part of the README file
says they are LGPLv3+, another part says they are LGPLv3.  This is confusing;
moreover, while the former is compatible with Savannah hosting requirements,
the latter is not.

Can you find those two respective parts of your README file?

> > Now, let us come to the license notice.  First, please repeat what > it
> should look like in case of releasing a package under the LGPL 'version 3 or
> later'.
> 
> Here is the license notice, I copied and altered it from this
> file(https://www.gnu.org/licenses/gpl-howto.html):
> 
> This file is part of StoneValley.
...
> You should have received a copy of the GNU Lesser General Public License
along
> with StoneValley.
> If not, see <https://www.gnu.org/licenses/>.

Correct.

> > Then, please note that Savannah hosting requirements include 
> > releasing documentation in GFDL-compatible way.  Can you see what 
> > that means?
> 
> Yes, that means all the releasing documents should be GNU Free Documentation
> License compatible.

To be on the same page: documentation files describe how to use your package,
how it works, and so on; in particular, README is a documentation file.

You should know that both GPL and FDL are copyleft licenses.  Copyleft,
basically, means that the work is free, and its license requires that any
works derived from it must be free as well,
https://www.gnu.org/licenses/copyleft.html

For copyleft license it typically means a requirement that the derived works
be under the same license, that makes such licenses incompatible with other
copyleft licenses.

Have you any questions?



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/task/?16584>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature


reply via email to

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