Kaj wrote about changes in the Enterprise and Community offering from MySQL AB – by the way, I still don’t understand why the Community VP delivers these announcements rather than a company press release. A Community VP’s blog can’t be the official publication channel of a PR department, can it?
I think Jeremy Cole summarises the issue very well. Important promises for the community ecosystem were not delivered. This is a great pity.
And no longer making the source tarballs of the Enterprise version publically available… come on. This should have been done from the start (and that’s not even a 20-20 hindsight statement 😉 It’s been blatantly obvious, really. It would have made sense, and is a perfectly valid choice under the GPL. Didn’t I write a blog entry on this exact model recently? But here’s the problem: first giving something (and various distros, like Debian, have been using them for their builds now) and then taking it away… that just looks bad.
I’ll note again that I want MySQL AB to do very well, business wise. It’d be good for the market, good for the product, and hey, it might be good for me at some point as I’m a (very minor) shareholder. But it takes time for a company to build karma with its community, while it’s very easy to burn it off.
Now, if the earlier public release enterprise source code release was a kind-of booboo that needed to be rectified, and this could have been presented in the light of all other community promises having been delivered…. I don’t think people would have been fussed, then. People would have understood (they’re smart), nobody’s perfect and mistakes are made. It’s the complete picture that’s the real issue now. Actual commitment and delivery (actions not words) is what it takes.