Code Contributing FAQ
Contents |
[edit] What is the purpose of the Code Contribution Program for MySQL AB?
From our own perspective, the purpose of the MySQL Code Contribution Program is
- to drive more fixes by the community to simple bugs, i.e. fix more bugs quicker
- to get more contributions in the form of new features, i.e. offer more features for our users
- to breed a larger recruitment base of developers familiar with MySQL both for our customers and ourselves
[edit] What are the benefits to the developer contributing to MySQL?
We believe that people contributing to MySQL are somehow scratching their own itch. Likely reasons why developers contribute to MySQL are
- to avoid having to maintain their patch, which they wrote just in order to fix their own problem with MySQL
- to increase their market value for recruitments, not just by MySQL AB but by any company
- to get feedback and users for their projects, by using MySQL as the wide-spread fundament of their (academic, research) project
We acknowledge that especially Category 1 people (and companies) consider all admin work to be bureaucracy. This is why we keep the paperwork and legalese to a minimum.
But we cannot go below the minimum. Our paying customers are sensitive to our IP (Intellectual property) rights. They are entitled to know for sure that we as their suppliers own what we sell them.
[edit] What are the terms of the CLA?
The MySQL Contributor License Agreement (CLA) means, in simple terms, that:
- The developer assigns and transfers the copyright of the contribution to MySQL to the extent permitted by applicable law. In return, the developer receives back a broad license to re-use and distribute the contribution.
- The developer grants a patent license to MySQL and its users, in the event that the developer owns a patent that covers the contribution.
- The developer represents that he or she coded and owns the contribution, and is legally entitled to grant the assignment and license.
- The developer may provide support for free, for a fee, or not at all.
- MySQL has no obligation to accept or use the contribution.
If MySQL accepts and maintains the contribution, and it is deemed of material value to the Project, the developer’s benefit is that we relieve the developer of the burden of maintaining the contribution and will provide the developer attribution in the GA release notes (unless the developer asks not to be mentioned). The developer may also select two of the following items: a MySQL Press book, a MySQL shirt, a US $100 rebate to a conference or training class, or a US $100 donation to the Free Software Foundation (FSF) by MySQL AB.
[edit] How do I agree to the terms of the CLA?
We have set up a web page on the MySQL Forge that aids you through the process. It requires you to fill in some personal information and to agree to the terms by clicking the "Accept" button at the end of the form. This information is then submitted to MySQL via email, a copy of the message will be sent to you as well.
[edit] Why does MySQL AB require copyright transfer? Red Hat does not!
The GNU Project does.
MySQL is the owner and copyright holder of the entire MySQL product, whereas Linux does not have one single entity as a copyright holder. This makes the MySQL Dual Licensing model possible. The MySQL users benefit from this in the form of further product development financed by MySQL (with currently over 80 developers on MySQL’s payroll). While MySQL has developed most of the MySQL database itself, and continues to do so, MySQL also wants to simplify the processes for contributors to MySQL.
[edit] Caveat for Europe
We received some comments on legal issues related to some European jurisdictions (notably Germany). This means that the CLA is still under development, and may receive some updates to improve its global reach in the near future.