While many have declared that there simply is no chance that proprietary code could be in Linux or other major open-source projects, concerns over these issues have led to the creation of companies to address these issues. Such businesses include New York-based Open Source Risk Management, which offers a vendor-neutral open-source indemnification insurance program, and Black Duck Software, which offers a system for checking source code for unauthorized use of open source code. The OSDL has committed to providing resources to ensure that contributions made to the kernel adhere to the DCO and the process improvements. The Lab will review the content of the contributions to confirm that submissions to the kernel have been signed off by contributors in accordance with the DCO. In addition, the OSDL plans to launch an educational campaign for developers and end users on the DCO and the process improvements."By making a contribution to this project, I certify that: (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it." The DCOs full text can be found at the OSDLs Linux Developers Certificate of Origin Webpage. Check out eWEEK.coms Linux & Open Source Center at http://linux.eweek.com for the latest open-source news, reviews and analysis.
The DCO itself is extremely simple. In its entity, it reads :