Linked by Thom Holwerda on Wed 18th Oct 2006 16:58 UTC, submitted by wirespot
Databases The popular MySQL database is slated for a future split between what MySQL AB calls the Community and the Enterprise versions. Read the official announcement and further opinions and explanations from Kaj Arno (MySQL VP of Community Relations) and Stephen O'Grady (software industry analist). In Arno's own words: "We recognise that the needs of the MySQL Community are different from the needs of commercial enterprise customers. After 11 years of producing our software, we can no longer hope that a single offering is the best solution for both Community and Enterprise users. Consequently, we are introducing two different offerings for each distinct target group."
Thread beginning with comment 172951
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Should have seen this coming.
by borat on Thu 19th Oct 2006 05:10 UTC in reply to "Should have seen this coming."
borat
Member since:
2005-11-11

Seems to be the way open source software companies work. Put out a free version, get people hooked, wait();, create two version
...
Oh well, more power to them, I'm sticking with pgsql.


WOW. good job not reading the linked articles at all mr. pgsql fanboy, nice way to harvest mod ups.

We believe the users of MySQL Community Server expect

* early access to MySQL features under development
* that MySQL AB will listen to their input
* timely corrections to bug fixes they report
* help with enhancing MySQL for their particular needs
* channels to communicate with the rest of community for getting assistance
* an easier process for having contributions accepted in MySQL
* commitment to Open Source — including free, unrestricted availability of source code

and this is what we will continue to deliver.

We’re happy to note the growth in contributions flowing into MySQL and its ecosystem. To facilitate these, we have

* launched MySQL Forge (see forge.mysql.com)
* established a Contribution License Agreement (see MySQL_Contributor_License_Agreement on Forge Wiki)
* supported a MySQL Community Camp (see mysqlcamp.org)
* started to Doxygen comment our code for easier understandability (see CommunityDoxygenProject on Forge Wiki)


mysql ab has been very good to the open source community and has no interest in changing that. they need a separate product for enterprise customers who don't want bleeding edge features, they want stability and consistent release cycles. this is nothing new: redhat/fedora, sun/opensolaris.

As part of our differentiation, we will do more frequent binary releases of the MySQL Enterprise Server software than of the MySQL Community Server. However, all of our database software is open source, so we will continue to make all releases available over our BitKeeper tree and as source code tarballs — even if the MySQL Enterprise Server binaries will not be available for public download but limited to our commercial customers and our core QA contributors.

Finally, we will continue to be active good citizens in the greater Free and Open Source Software world. We’re participating in the GPLv3 drafting process, we’re supporting the Free Software Foundation as FSF corporate patrons, and we’re supporting campaigns against the spread of software patents around the globe.


Edited 2006-10-19 05:12

Reply Parent Score: 0