Wednesday Sep 21, 2011

Contributor agreements, a reminder and an update

One of the many things that hasn't changed with GlassFish since the acquisition is how we welcome contributions from the community (in fact we've seen an increased number of those recently).


The Oracle Contributor Agreement, or OCA (born as the SCA) is a required document before we can accept such contributions and a fairly common practice in open source projects. One important thing that has changed for the OCA is the email address to use for signed contributor agreements. Check this Contribute Code section for details.

One thing that will change is the location of the public list of the OCA signatories. For the time being you can find a consolidated and updated list for GlassFish, OpenJDK, NetBeans, MySQL and more on

The OCA FAQ document (which is still frequently being updated) lists a good number of answers to questions such as "What does the OCA do?", "Why do you have a Contributor Agreement?", "What if I'm contributing on behalf of my company?", "What can Oracle do with my contribution?" and many more.

Thursday Oct 02, 2008

MySQL adopts Sun Contributor Agreement


Until a few months ago, the MySQL community had several complaints about the contribution process. The two biggest obstacles were an unfriendly revision control system and a too demanding contributor agreement.

The revision control system was changed in June. Exit BitKeeper, enter Bazaar. And now goes the second obstacle. Today, Kaj Arnö announced that MySQL has adopted the Sun Contributors Agreement. Kudos!

There are still a few impediments, but the database group management seems well determined to tackle the problem and become contributions friendly. There is more in the making. Stay tuned!