Yes, I believe that your point of vision is right. I believe that inverse position is true: how can we guarantee that those working in GPL/commercial version are not seeking LGPLed fixes/improvement?
The FISRT thing we WON'T is "copy" illegally their work. We don't want this. All that we want is to be legal. And maintain all things legal too (and if we change to GPL will not be anymore). We need volunteers to help us to be legal (the ones that know things about law - specially international law), that should be giving some time to analise and direct us to right way. If you search the web you will find 2 or 3 JDBC drivers to connect to MySQL. And you'll find even for the MS SQL Server/Sybase open source initiatives... They are not illegal, even existing several commercial efforts. For Interbase, I've found 3 commercial ODBC drivers, and 1 open source. None of them are illegal. Neither one is copy of another, as far as I can see different bugs in each. And we can find Firebird and Interbase versions of JDBC drivers. We will be maintaining LGPLed versions (really I can tell you I'll be personally involved with JDBC driver) will be maintained even protocol changes radically). The same (AFAIK) occur for ODBC/Perl/Python/.Net (that needs to be created), etc. Edson Richter ----- Original Message ----- From: "Matt Benjamin" <[EMAIL PROTECTED]> To: "Edson Carlos Ericksson Richter" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, June 06, 2003 11:10 AM Subject: Re: SAP DB and MySQL: Short-term plans Edson, I support this effort, but, as I was trying to imply in my original post, there are some issues that I hope will be considered. Primarily, if this is a serious effort, it will be necessary to ensure that any modification, even entire replacement, of the wire protocol for SAPDB access can be implemented by the LGPL libraries, and also to ensure that there is a legally-defensible firewall between the GPL source code released by MySQL, and the LGPL libraries. I think MySQL will be diligent in defending their franchise rights over the next generations of SAPB, as they should be. I believe that if the LGPL libraries are to avoid a legal quagmire that could end the project, they will need to be able to show that people working on the LGPL source code have not seen the corresponding MySQL source code. They may need to be able to defend the integrity of every line of code. It might be possible for a third party to construct an specification of changed or new behavior and data structures, and share that with developers--but I'm not sure, IANAL. But some legal guidance might be required to get it right. Matt On Fri, 2003-06-06 at 08:53, Edson Carlos Ericksson Richter wrote: > Hey, community don't worry about change from LGPL to GPL. > > I can confortably say this because the same community WILL be maintaining > LGPL versions of thoose libs. > We are watching for volunteers to work on this. We already have about 10 > volunteer team members, incresing one each day. > We are not fully orgnized (we don't have a "starting point" as site, neither > SourceForge, neither others), but we are in the direction. > > And more, we can join the ones that are working in recongnized projects in > SourceForge, as .Net data provider initiative, and the DMBJui server > administration utility initiative. > > I think MySQL || SapAG should revise their efforts and join us, that will be > doing this - without changing license model, and we aren't "charities" too. > We will be giving our time that will be paid by incomes due to use of this > LGPLed libs in our commercial products. It's more than just. > > Think right, be volunteer. > > Best regards, > > Edson Richter > > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.487 / Virus Database: 286 - Release Date: 1/6/2003 > > _______________________________________________ > sapdb.general mailing list > [EMAIL PROTECTED] > http://listserv.sap.com/mailman/listinfo/sapdb.general -- Matt Benjamin The Linux Box 206 South Fifth Ave. Suite 150 Ann Arbor, MI 48104 tel. 734-761-4689 fax. 734-769-8938 cel. 734-216-5309 _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.488 / Virus Database: 287 - Release Date: 5/6/2003 _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
