[task #16584] Submission of StoneValley

[Ineiev]

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


> I am sorry I made confusions to you. I mean, since requiring a copy of LGPL
a
> the source tarball is a set of additional permissions, and I may at my
option
> remove any additional permissions, it says the license gives the right to me
> to determine whether add or remove the copy of license.

I'm afraid this still sounds confusing to me.  We have discussed that
the copyright holders were not bound by the licenses they apply to
their programs.  Don't you remember that?

> > To make sure that we are on the same page: do you mean file #56448?
> Did you attach the correct file?
> 
> Yes, it is file #56448. I attached the correct file.

Then I wonder how you listed the files to check in your tarball,
and how you checked them.



___

Reply to this item at:

  

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


signature.asc
Description: PGP signature

[task #16584] Submission of StoneValley

[John Cage]

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


> I'm afraid this still sounds confusing to me.  We have discussed that
> the copyright holders were not bound by the licenses they apply to
> their programs.  Don't you remember that?

Yes, I remember. The license can not restrict what the copyright holders
choose to do. However, as a man who wants to convey library to others under
LGPL license, I may use the license as a guide to add or remove a copy of the
license itself. Though it is not compulsory to bind license with the project,
I choose to add both GPL and LGPL with StoneValley project.


> Then I wonder how you listed the files to check in your tarball,
> and how you checked them.

I follow this guide:

> You sent me the link mentioned these following 2 types of  copyrightable
> files:
>
> a) For copyright purpose, any file more than ten lines long is nontrivial,
so
> it should have copyright and license notices.
>
> b) 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.

1st, I add copyright notice to the README files shows this whole project is
published under the LGPL license.

2nd, Every file more than 10 lines long is added with copyright notice.



___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/


signature.asc
Description: PGP signature