Re: [task #16584] Submission of StoneValley

[Ineiev]

> > I don't think I understand what 'use the license as a guide' means.
> 
> As the previous conversations mentioned the LGPL and the GPL license can't
> force copyright holders what to do, at the same time, if I want to send
> StoneValley to others, I am also conveying a package, so I (as the copyright
> holder and both package conveying man) may use the GPL and LGPL as a guidance
> to convey packages. The GPL license notices us to convey packages with the GPL
> license, therefor, I can convey StoneValley with GPL and LGPL license.

The GPL has a section for the copyright holders after the end of terms
and conditions, "How to Apply These Terms to Your New Programs".
Since other parts are written for the recipient do you refer to that
section when you say 'guidance'?  But then the LGPL contains no such
section.  Do you mean something else?

> I think it is the user's rights to know their rights to treat with a tarball
> file.
> 
> So, when the tarball comes with a copy of the LGPL will explicitly show users
> what to do and what not to do.
> 
> When the tarball comes without a copy of the LGPL, users can not immediately
> know their rights to treat tarballs. Sometimes they have to connect to the
> internet and download LGPL license from GNU's website, thus indirectly convey
> tarball and implicitly shows the license.

This isn't just about having to find a copy fo the LGPL somewhere.
When the tarball contains no copy of the LGPL, the user can't tell
if it's because the distributor forgot to include it or because
the package was really relicensed, for instance, under the GPL.

> > Good; but I'd like to know how you get the list of the candidate files
> > to check in the first place.
> 
> I choose those program files whose line numbers greater than 10 to add legal
> notices:

The question is, how you find those files.

> I think copyright notice is:
> Copyright (C) <year> <full name>
> 
> It consists of a word Copyright, a copyright sign '(C)', the year or a range
> of years copyright takes in charge and the copyright holder's full name.

Magnificent.  Now we can see two points.

* Copyright notices don't specify the distribution terms of the package.
* README in file #56448 includes no copyright notice.

Can you see that?

>     _______________________________________________________
> 
> To reply to this notification, you have two options:
> * In the Web UI at <https://savannah.nongnu.org/task/?16584>.
> * By email, ONLY IF you sign your email with a GPG key registered
>   in your Savannah account AND you include the following line
>   in the reply:
> 
>   {savane: user = 46355; tracker = task; item = 16584}
> 
> _______________________________________________
> Message sent via Savannah
> https://savannah.nongnu.org/

signature.asc
Description: PGP signature