Hi,
A fork can be a very destructive thing if it breaks a project that
could be strong into smaller projects. I agree that if MySQL does not
allow the ODBC/JDBC to be used under LGPL or something similar, we should
start a fork, but let's wait to hear from them on this. Trust me, I work
for a fortune 50 company, and we will not let SAPDB be suddenly turned
into a pay-only project, nor GPL all of our software. Having an option
-between- the free email support and the $60K US per year SAP wanted for
dedicated support would be nice though. Perhaps MySQL will realize they
can make money from this and boxed sets (which we would also buy). We
can't complain until we know what MySQL is going to do, so let's wait and
see. If a fork is warranted, I will be first in like to maintain it, but
if MySQL is reasonable, we should support them, as it will be good for
both sides. Their idea of adding MySQL Protocol support to SAPDB is
especially a good idea (and one I experimented with before, actually),
because it will allow MySQL to be more easily integrated with the dozens
of apps that have out-of-the-box support for PG-SQL and MySQL.
Thank you,
Noah Silva
IS&T - Programmer Analyst
ATOFINA Chemicals
(215) 419 - 7916
"ajit_cus" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
06/01/2003 11:47 PM
To: <[EMAIL PROTECTED]>
cc:
Subject: SAPDB fork
It looks as if the first release of mySQL-SAPDB is not
going to be loaded with new features, so I don't really see any reason
that current SAP-DB users will move to it.
I see a few people showing an interest in maintaining a fork of the
current client libs(kernel too?). I would personally be interested in
contributing time and effort to such an initiative.
Regards,
Ajit
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
