On Tue, May 29, 2012 at 5:10 PM, mmarco <mma...@unizar.es> wrote: > I have contacted the author of the kbmag package (which has no > copyright note at all), and he told me that "it is distributed under > no license, it is completely open source". I have asked him permission > to distribute it under the gpl license. So i have a legal question: > would it be enough if he gave me permission to do so to include it in > sage (either in the gap_packages spkg or in a separated package)?
Yes, but better would be to send him the actual text of the license (summarized in a paragraph inside the email) and ask him to explicitly agree to it or not. It would also be nice if you could get him to agree to GPLv2+, which means "GPLv2 or later". > > On 29 mayo, 13:30, mmarco <mma...@unizar.es> wrote: >> You are right, i didn't think about the license. Still, my point is >> valid even if we restrict it to GPL gap packages. >> >> On May 29, 12:54 pm, David Joyner <wdjoy...@gmail.com> wrote: >> >> >> >> >> >> >> >> > On Tue, May 29, 2012 at 5:50 AM, mmarco <mma...@unizar.es> wrote: >> > > One of the complains i have heard from my colleagues that use sage >> > > (and i have noticed myself) is the lack of certain gap packages in the >> > > sage distribution. There is an spkg with some of them, but most are >> > > missing. Also, it is not easy to find documentation on how to install >> > > gap packages in the sage installation. I propose some possible >> > > solutions for that (not necesarily exclusive): >> >> > > 1) increase the amount of gap packages in the gap_packages spkg >> >> > The GAP packages have various distribution licenses. Just because they >> > are distributed on gap-system.org doesn't mean anyone can distribute >> > them. It depends on the license. You could either check that the >> > redistribution is allowed (eg, if the package is GPL'd) or, if needed, >> > contact the package authors directly. Alternatively, you might be >> > able to write a script (using wget?) which downloads the packages >> > from the GAP website then installs them automatically. >> >> > > 2) Do some extra spkg's, maybe one for each gap package? >> > > 3) Related with the previous one: write some quick guide on how to >> > > make those extra spkg's, and add it to the documetation (maybe tthe >> > > wiki would be a good place for that). I know there is a chapter on the >> > > developement guide about spkg's, but in this case i mean something >> > > like an easy step-by-step guide. This could be useful for people that >> > > want to add a certain gap package, and also their effort can be reused >> > > if those packages are collected somewhere. >> > > 4) Just write some documentation on how to install gap packages by >> > > hand. >> >> > > I can volunteer for both options 2 or 3 (and maybe 4, although i am >> > > sure there are some people that would do much better than me), but i >> > > would like to know what people think first. >> >> > > -- >> > > To post to this group, send an email to sage-devel@googlegroups.com >> > > To unsubscribe from this group, send an email to >> > > sage-devel+unsubscr...@googlegroups.com >> > > For more options, visit this group >> > > athttp://groups.google.com/group/sage-devel >> > > URL:http://www.sagemath.org > > -- > To post to this group, send an email to sage-devel@googlegroups.com > To unsubscribe from this group, send an email to > sage-devel+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org