MySQL

The world's most popular open source database

Contact a MySQL Representative


  • MySQL.com
  • Developer Zone
  • Partners & Solutions
  • Customer Login
  • DevZone
  • Downloads
  • Documentation
  • Articles
  • Forums
  • Bugs
  • Forge
 
  • Pages

    • Press Release: “Kaj Arnö Appointed MySQL VP of Community Relations”
  • Archives

    • May 2008
    • April 2008
    • March 2008
    • February 2008
    • January 2008
    • December 2007
    • November 2007
    • October 2007
    • September 2007
    • August 2007
    • July 2007
    • June 2007
    • May 2007
    • April 2007
    • March 2007
    • February 2007
    • January 2007
    • December 2006
    • November 2006
    • October 2006
    • September 2006
    • August 2006
    • July 2006
    • June 2006
    • May 2006
    • April 2006
    • March 2006
    • February 2006
    • January 2006
    • December 2005
    • November 2005
    • October 2005
    • September 2005
  • Categories

    • Architecture of Participation (42)
    • Connectors (12)
    • Documentation (4)
    • Events (42)
    • Falcon (5)
    • GPL (7)
    • GUI (3)
    • Licensing (9)
    • MySQL (187)
    • MySQL Cluster (4)
    • MySQL Proxy (4)
    • MySQL Server (27)
    • MySQL Users Conferences (24)
    • MySQL Workbench (5)
    • Photography (11)
    • PHP (9)
    • Release Policy (17)
    • Ruby on Rails (5)
    • Running (3)
    • Summer of Code (8)
    • Sun (39)
    • Sun visits (21)
    • Travel (18)
    • Use cases (6)
    • Virtual company (34)



Kaj Arnö
« How to Now Contribute Code to MySQL
Making MySQL Linux Standard Base 3.1 compliant »

Code Contributions & Consideration

Consider this:

You create a piece of code that is truly valuable for MySQL. We give you a T-shirt. Does this feel right?

Of course it doesn’t. The CLA (Contributor License Agreement) just contains the T-shirt as a default so-called consideration and a token of appreciation. Several people rightly reacted to the imbalance of T-shirts versus valuable code in my original CLA post.

The legal concept of “consideration” in American or English law means more-or-less compensation, i.e. a countercommitment to make the contract not just balanced but enforceable. Wikipedia’s definition of consideration starts like this:

Consideration is defined as a bargain for the exchange of something of value. An example of consideration is the sale of a car for payment (e.g. the sale of a Toyota for $3,000). Consideration is a central concept in the common law of contracts. Under classical contract theory, consideration is required for a contract to be enforceable.

In several cases during the history of MySQL, consideration for code contributions has been money and shares of MySQL AB. On a case by case basis, serious money can move hands. We don’t mind paying good money for good contributions. MySQL AB is not a charity, nor do we expect code contributors to be charities towards us.

For quite a number of contributors, I still expect the major consideration to be that we take over the maintenance burden of the patch. And for many contributors, the code contributed may be interesting for some MySQL users, but not for large enough numbers to merit “serious money”.

Some contributions are just the starting point of code patches that can be accepted into the code base, complying to coding standards and having gone through the scrutiny of reviews. But rest assured, if you fix bugs in the form of acceptable code patches, there will be much more than just T-shirts coming your way!

With contributors of gems, we have not just agreed for them to join MySQL AB (like Mark Matthews for Connector/J) but compensated them with cash and/or shares in MySQL AB. Such transactions happen after relations have been built up long-term.

This entry was posted on Wednesday, July 26th, 2006 at 20:13 and is filed under Architecture of Participation, MySQL. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

Leave a Reply

Kaj Arnö is proudly powered by WordPress MU running on Blogs.mysql.com.
Entries (RSS) and Comments (RSS).