Just in case it wasn't clear from Hakan's post, we are opening up the next Monty Program company meeting in October 7-12 to be a general MariaDB developers meeting. (In fact, we've had a few guests in all of the previous meetings too, but now it's formal and public.) Ever since Sun folded this annual MySQL AB tradition (to save money) there has been people asking when the next meeting would be, since for the developer community outside MySQL AB it was the main networking and information sharing event of the year. Last MySQL user conference we agreed that something needs to be done, and this is it. If you work on any of the MySQL variants, a storage engine, or are otherwise interested in deep architectural MySQL/MariaDB discussions, you are welcome to join and should contact Hakan or My for details.1 The invitation of course also is valid for Oracle employees, in case you were wondering.

And that's the other significant news hiding in Hakan's post: My Widenius, an experienced traveller herself, will be in charge of meeting logistics. This means even My herself now works for MariaDB, and can be reached with my at mariadb dot org :-)

1. 1. If you are a Drizzle hacker, it is probably less interesting, but you are of course still welcome if you come! Anyway, we did also discuss having a similar developer meeting adjacent to an OpenSQL camp or something that could cover broader topics, and this is still an option. But as it is now, this is a MySQL/MariaDB focused meeting and there already was a separate Drizzle Developer day and we can just see what else is needed.

The Open Content revolution has happened! ...it just didn't happen in the way we expected it.

I was recently interviewed for a London music blog Music 4.5: What the music industry can learn from the open source movement?1 Somewhat surprisingly, I gave Youtube as an example of a website where music and video is re-used in an open source fashion:

1. 1. Funny story, I was introduced to Charlotta Hedman by my former MySQL Ab collague Mark Baker, also from London, without him knowing that we are both from the small Finnish city of Jakobstad and I even worked for her dad as a teenager.

Inspired by my previous blog about the Lastwear open clothing company, I decided it is again time to take the pulse on how open source is spreading outside of the software world. The last time I did this was in 2008, where I concluded:

I was recently pointed to a startup called Lastwear, who has gotten their seed funding via Kickstarter.com (also a new acquaintance to me). With an eye to the topic of this blog and namesake book I wrote some years ago, this is some great news in so many ways.

Much has been said about open core, but with the OSI coming out squarely against it on the one hand, and Rackspace and NASA creating the OpenStack.org project as a "true open source replacement" for Eucalyptus on the other hand, it seems open core is now much less attractive than it was only a week ago. It seems everyone has now learned what open core is and agrees that it is not open source, nor is it good for open source. (And by "everyone" I mean everyone that really are open source advocates, naturally those who directly or indirectly are trying to profit from open core will continue to promote the model for a long time to come.)

The final question that remains to be answered is, if I know about open core and don't like it, what can I do to help prevent its spreading and rather promote the adoption of true open source?

With my personal experience working for MySQL, I've had a few years to collect some ideas, and would like to share them below. Please add your own in the comments and I'll keep updating this post so it can remain a useful reference.

(Last updated Aug 29, 2010.)

The past week more and more people weighed in on the open core debate. Personally, I don't have much more to add now and it seems I have been able to articulate why it is bad and against open source. Watching some of the comments of this week it also seems that the more people talk/write about it, the more their true thinking and motivation becomes apparent to everyone. So rather than add more words, I will just highlight what others are saying.

Watching the discussion last week reminded me of a friend in university, who was a vegetarian. This was becoming popular at the time. I once then saw her ordering a chicken pizza, so I mentioned that she is not a vegetarian after all. This upset her and she protested that who am I to judge her and surely just because she eats chicken doesn't mean she is not a vegetarian.

Now unto the open core debate...

A lot has been written for and against open core now. Yet in the end, a couple tweets can catch all that is needed:

scurryn @h_ingo -- So as long as 'an open core vendor' doesn't call themselves 'an open source vendor' then everything's fine?

h_ingo @scurryn: pretty much. I think I owe everyone one more blog post to answer that question with a few more details.

(Twitter)

This is that blog post.

My ongoing dialogue with Matthew Aslett inspired me to read more of his recent writings. An excellent piece Do not sell anything to your community is based on a blog post by Stephen Walli.

Inspired by Stephen, I also looked into a set of slides I recently created and will try that style for this post...

Aslett and Stephen make a great point:

the conversion of community users into paying customers has long been a concern for open source-related vendors. It has also long been a source of friction, with vendors that offer proprietary extensions being accused of “bait and switch” or otherwise undermining the value of the open source software in an attempt compel community users into becoming paying customers. In recent years the next generation of start-ups has learned that the best way to encourage a frictionless relationship between a vendor and its community is not to attempt to “convert” users at all.