On Wed, 2002-04-24 at 21:55, Shawn Walker wrote: > According to the COPYING document, it's seems like that you *should* > be releasing the source to the Exchange Connector because you are in > fact putting the source under a GPL and that would seems like that you > have to following the GPL rule. I didn't see anything any documents > that you or Ximian is excluded from the GPL agreement.
We own the copyright, therefor we have the legal right to write extensions to it under any license we choose. We can dual license code that we own. That's the way the world turns... Just like Netscape can dual license Mozilla. > > If there is something in the license that you (Ximian) are excluded > from the GPL license, then where is it? I'm just trying to clear up That spot is right here: Copyright 2000-2002 Ximian, Inc. (www.ximian.com) > some issues because I do have a problem that you guys (Ximian) is > putting yourself in a different position than the rest of us that want > to write a plugin but denying us the opportunity to make some money > for our hard work to help promote your product. Maybe you can talk to our business people and license the code from us so that you can license your plugin under whatever license you want. But short of that, you have to obey our license, which is that all derivative works must be licensed under the GPL. Jeff > > On 4/23/2002 at 9:56 PM Jeffrey Stedfast wrote: > > >Ximian owns the copyright to all of Camel, therefor they could license > >the Connector any way they wanted to. > > > >Jeff > > > >On Tue, 2002-04-23 at 21:56, Shawn Walker wrote: > >> GPL? Then why didn't Ximian GPL-ed the Exchange module then? > >> > >> So much for me coming up with a module that I wanted to do. > >> > >> On 4/24/2002 at 9:37 AM Not Zed wrote: > >> > >> >Simplest example is probably NNTP, its the newest (cleanest?) code, > >> >although it isn't complete yet. > >> > > >> >Remember they have to be mt-safe, and GPL of course. Much of the > >> >functionality is inherited from the base classes, so a minimal > >> >implementation can be quite small. > >> > > >> > > >> >On Wed, 2002-04-24 at 03:33, Jeffrey Stedfast wrote: > >> >> The documentation is kinda lacking, but there are lots of examples, > >just > >> >> look at evolution/camel/providers/* > >> >> > >> >> Jeff > >> >> > >> >> On Tue, 2002-04-23 at 09:35, Shawn Walker wrote: > >> >> > How do I write a Camel Provider/Store? Is there any documentations > >> >and samples? > >> >> > > >> >> > Thanks! > >> >> > > >> >> > > >> >> > _______________________________________________ > >> >> > evolution-hackers maillist - [EMAIL PROTECTED] > >> >> > http://lists.ximian.com/mailman/listinfo/evolution-hackers > >> >> > > >> >> -- > >> >> Jeffrey Stedfast > >> >> Evolution Hacker - Ximian, Inc. > >> >> [EMAIL PROTECTED] - www.ximian.com > >> >> > >> >> > >> >> _______________________________________________ > >> >> evolution-hackers maillist - [EMAIL PROTECTED] > >> >> http://lists.ximian.com/mailman/listinfo/evolution-hackers > >> > >> > >> > >> > >> _______________________________________________ > >> evolution-hackers maillist - [EMAIL PROTECTED] > >> http://lists.ximian.com/mailman/listinfo/evolution-hackers > >> > > > > > >_______________________________________________ > >evolution-hackers maillist - [EMAIL PROTECTED] > >http://lists.ximian.com/mailman/listinfo/evolution-hackers > > > _______________________________________________ evolution-hackers maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution-hackers
