openark-kit, Facebook Online Schema Change, and thoughts on open source licenses

MySQL@Facebook team have recently published an Online Schema Change code for non blocking ALTER TABLE operations. Thumbs Up!

The code is derived from oak-online-alter-table, part of openark-kit, a toolkit I’m authoring. Looking at the documentation I can see many ideas were incorporated as well. And of course many things are different, a lot of work has been put to it by MySQL@Facebook.

openark-kit is currently released under the new BSD license, and, as far as I can tell (I’m not a lawyer), Facebook’s work has followed the license to the letter. It is a strange thing to see your code incorporated into another project. While I knew work has begun on the tool by Facebook, I wasn’t in on it except for a few preliminary email exchanges.

And this is the beauty

You release code under open source license, and anyone can pick it up and continue working on it. One doesn’t have to ask or even let you know. Eventually one may release back to the community improved code, more tested (not many comments on oak-online-alter-table in the past 18 months).

It is a beauty, that you can freely use one’s patches, and he can then use yours.

And here is my concern

When I created both openark-kit and mycheckpoint, I licensed them under the BSD license. A very permissive license. Let anyone do what they want with it, I thought. However Facebook’s announcement suddenly hit me: what license would other people use for their derived work?

The OSC has been release under permissive license back to the community (again, I am not a lawyer). But, someone else could have made it less friendly. Perhaps not release the code at all: just sell it, closed-source, embedded in their product. And I found out that I do not want anyone to do whatever they want with my code.

I want all derived work to remain open!

Which is why in next releases of code I’m authoring the license will change to less permissive and more open license, such as GPL or LGPL. (Of course, all code released so far remains under the BSD license).

20 thoughts on “openark-kit, Facebook Online Schema Change, and thoughts on open source licenses

  1. hi.

    haven’t you thought about this kind of situations before?
    I mean it’s weird that you change your license, after somebody actually do-what-they-wanted-and-the license-allowed-to-do.

    Tyrael

  2. @Tyrael,
    Well, people change their minds 🙂
    I’m happy with the use made so far to my code. I have just realized how important it is for me that the code remains open: for me, for you, for everyone.

  3. though I’m not alleging anything about this exact case neither do I represent positions of affected parties, I just wanted to say that more restrictive licenses may be the reason your code will not be reused and you will not get attribution.

    also, GPL will not force people to opensource their modifications, so you will not win openness.

    whatever license you pick, it applies to redistribution only, and nobody is obliged to redistribute, only the method of redistribution is shaped by license texts.

  4. Hi Domas,
    Thanks. You were sure careful to pick your words 🙂 No reason to.

    You are right that GPL will not force people to opensource their modifications, if they never release them.
    But should someone choose to distribute a commercial product, then he/she is affected by the GPL.

    “…more restrictive licenses may be the reason your code will not be reused…” – I need to think this over

    “…and you will not get attribution…” – this is not my concern. It’s not a matter of glorification.

    Thanks

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.