Hello Glynn,<br>
thanks for your suggestions. More below ...<br><br><div class="gmail_quote">2009/8/18 Glynn Clements <span dir="ltr"><<a href="mailto:glynn@gclements.plus.com">glynn@gclements.plus.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
Soeren Gebbert wrote:<br>
<br>
> > > > If it's being included in the main GRASS tree, it would be simpler to<br>
> > > > relicense it as GPL.<br>
> > ><br>
> > > So we have to convince the author Daniel A. Atkinson<br>
> > > to relicense the ccmath library as GPL code?<br>
> ><br>
> > The LGPL explicitly permits relicensing to GPL:<br>
> ><br>
> > 3. You may opt to apply the terms of the ordinary GNU<br>
> > General Public License instead of this License to a given<br>
> > copy of the Library. <snip><br>
> ><br>
><br>
> I do not understand. What to do now?<br>
> Will we keeping the LGPL??<br>
<br>
</div>I don't particularly mind, but I do think that we need to be careful<br>
about contributions.</blockquote><div><br>Ok, i fully agree. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
When the overall project is licensed under the GPL, it's reasonable to<br>
assume that any contributions are also licensed under the GPL. If<br>
someone contributes changes to a file which happens to be LGPL, they<br>
might have actually intended to license their contribution under the<br>
LGPL, or they might have just overlooked that the file in question is<br>
LGPL. Also, it means that you can't copy or move code from another<br>
part of GRASS into that library.</blockquote><div><br>1.) I can extend the SUBMISSION file to explain that any new numerical or mathematical code belongs into the grass gmath or gpde libraries. The ccmath lib is connected to grass via a wrapper in the gmath lib. Only the wrapper (a single C file) includes the ccmath header. The gmath header only knows the wrapper functions. So nobody should include the ccmath header directly besides the wrapper.<br>
<br>2.) We can make a guideline that only bug-fixing is allowed in the ccmath library (README.txt in ccmath dir). The grass ccmath part must be compatible with the 2.2.1 version of ccmath to enable external linking. IMHO i in the near future nobody will contribute to the ccmath part in
grass, because the code is hardly readable and not easy to maintain.<br><br>3.) I can place an ATTENTION.txt file in the ccmath library folder, which explains the licensing issue. <br><br>If this is ok, i would like to submit my changes to svn. <br>
<br>Best regards<br>Soeren <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<font color="#888888"><br>
--<br>
</font><div><div></div><div class="h5">Glynn Clements <<a href="mailto:glynn@gclements.plus.com">glynn@gclements.plus.com</a>><br>
</div></div></blockquote></div><br>