I actively talk with Sebastien (the author of wicket-jquery-ui). His project consist of different parts with different licences (for example Kendo* plugins are GPLv3 licensed) I only took parts licenced under compitible licenses.
I can write him a letter to add NOTICE, should I? For the changes to the FullCalendar I would: 1) read the documentation (it has 'ignoretimezone' option which might help 2) take a look at the current issues, for ex. this one https://github.com/arshaw/fullcalendar/pull/92 3) propose the patch to the author 4) hacking ourselves :) On Thu, Aug 1, 2013 at 8:48 AM, [email protected] <[email protected] > wrote: > Okay but it seems like it is Apache Licensed: > https://code.google.com/p/wicket-jquery-ui/ > > But wicket-jquery-ui includes other libraries that are under the MIT > license. So he would need a NOTICE file (According to our rules). > > Its really a bit messy, I think we should clean that up and add the > FullCalendar to our NOTICE file to make sure nobody raises concerns about > the legal status of our project. > > Sebastian > > > 2013/8/1 [email protected] <[email protected]> > > > I am afraid some of our changes that are required for instance for making > > it timezone safe will be much easier if we simply do it. > > And also their use will be relatively limited to what we want to do with > > it. So its unlikely that it will be useful for anybody else. > > > > We can then discuss how and when those changes will become part of > > wicket-jquery-ui. > > > > For me it seems like the author of wicket-jquery-ui does not care about > > the license at all. There is not even a License file or any kind of > header > > in the source code of his file. > > So in theory that can literally mean that he can decide tomorrow he will > > license it under whatever he wants it to be. > > > > That is a bit scary for us. We can't just include a library without > having > > a correct attribution of the License. > > > > I know there was put a bit of effort into using this library now, but if > > we release it and there will be doubts raised about this it could mean we > > have to replace the entire library. > > > > Was anybody able to actively talk to the author of that wicket-jquery-ui > ? > > Cause if that guy does not respond to any emails its really kind of > > dangerous to base our application on the hope he will not suddenly change > > his mind and put the code under a license we don't like. > > > > Sebastian > > > > > > > > > > > > 2013/8/1 Maxim Solodovnik <[email protected]> > > > >> Hello Sebastian! > >> > >> we actually do not distribute the fullcalendar.js. > >> We are using wicket-jquery-ui which ships fullcalendar for as. > >> > >> Despite wicket-jquery-ui allows to replace almost any resource with > custom > >> one, I would start from proposing our patch to the author since it would > >> be > >> easier to maintain in the future. (Already was done with > wicket-jquery-ui, > >> wicket and some jquery libraries) > >> > >> > >> > >> On Thu, Aug 1, 2013 at 7:36 AM, [email protected] < > >> [email protected] > >> > wrote: > >> > >> > Hi, > >> > > >> > the OpenMeetings project would like to redistribute the jQuery Plugin > >> > "Fullcalendar": > >> > http://arshaw.com/fullcalendar/ > >> > > >> > As part of its distribution. Which itself should not be a problem: > >> > http://www.apache.org/legal/3party.html#category-a > >> > > >> > But we also might need to modify some of the source code to fit our > >> needs. > >> > > >> > Are we allowed to do that? > >> > Are there changes to NOTES files needed when we do that ? > >> > > >> > I've somebody knows an answer to that or pointers to the FAQ where > this > >> > would be covered, I would much appreciate. > >> > But I think the FAQ don't cover that topic yet. > >> > > >> > Thanks, > >> > Sebastian > >> > -- > >> > Sebastian Wagner > >> > https://twitter.com/#!/dead_lock > >> > http://www.webbase-design.de > >> > http://www.wagner-sebastian.com > >> > [email protected] > >> > > >> > >> > >> > >> -- > >> WBR > >> Maxim aka solomax > >> > > > > > > > > -- > > Sebastian Wagner > > https://twitter.com/#!/dead_lock > > http://www.webbase-design.de > > http://www.wagner-sebastian.com > > [email protected] > > > > > > -- > Sebastian Wagner > https://twitter.com/#!/dead_lock > http://www.webbase-design.de > http://www.wagner-sebastian.com > [email protected] > -- WBR Maxim aka solomax
