Code Contributing FAQ
Contents |
[edit] What is the purpose of Contributing Code to MySQL?
From our own perspective, the purpose of Contributing Code 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 users 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 Sun Microsystems 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 administrative 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 SCA?
Contributors are required to sign the Sun Contributor Agreement (SCA) when contributing code to Sun/MySQL. The SCA is a short legal agreement which protects both you as a contributor and Sun/MySQL from legal attack. By signing the SCA, you agree that Sun/MySQL is legally allowed to use your code in Sun/MySQL software and that the code is, to the best of your knowledge, unencumbered by any patent issues.
[edit] How do I agree to the terms of the SCA?
A copy of the most recent version of the SCA can be found here (PDF). See this page for detailed instructions on how to submit your agreement.