On Tue, 2002-09-24 at 12:16, Andrej Falout wrote: > Maybe the temporary answer is to collect all patches provided by community. > Anyone?
Andrej, This could be a good thing. It would allow the SAP folks to utilise those patches which are deemed appropriate for their environment, while still maintaining access to fixes/features/bugs for the rest of us. In that context, maybe it works to think of it like the Linux kernel model, with contributors providing many patches, but only the ( benevilent-dictator | salary-paying-junta ) gets the say on what goes into the offically blessed code base... but there's nothing to stop anyone else patching their code as they see fit, if the resources are available. Most people will still use the offical code, but some will try the other stuff out. If feedback can be captured through lists or forums, we can all know what works for better or worse, and everyone can benefit. Also, if the "alternative" patches work better, are more portable, and end up becoming a fork, so be it - it'll only happen if there's a need. And yeah, I agree we could look at the Firebird model... (having said that, I know of local businesses using it to keep costs down for clients) Richard. _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
