GIVEN THAT,
The CAcert Community, being the Members who have agreed to the CAcert Community Agreement, desires the secure operation of a Certification Authority (CA),
CAcert Inc., being the Association registered in Australia, is charged with control and security of the Certification Authority, for and on behalf of the Community,
The critical application built of source code and documentation ("code") forms an essential component in that CA,
Contributors, being those developers that write and provide those very lines of code for the critical application, desire that the product created out of their efforts remain free and available,
Audit, being a control over the operations of the CA originally requested by Mozilla Foundation for the benefit of its end-users, desires that the control of the critical application be simple, direct, solid, and aligned with the Configuration Control Specification (a module of the Audit Criteria),
And,
The Members want to get their certificates without the normal hoopla of bureaucracy, crapola, feeism, committeemudism, licence wars and other geekery,
WE ALL DO AGREE THAT,
The source code for the critical servers is fully owned and controlled by CAcert Inc,
Excepting "External Code", being those packages from external well-formed software projects which are approved, documented, and aligned,
Contributers transfer all rights of ownership and control over to CAcert Inc for code written by them,
CAcert Inc licenses back to each Contributor a free, open and perpetual licence for the lines of code of that developer,
Developers upload either contributed code or External Code,
CAcert Inc. initially licences its source code under a GPL-compatible licence,
CAcert Inc. may make material changes to the regime of licensing, such as adding a new licence or retiring an old licence from time to time,
However the community of Contributors may veto any material change where voted on with a two-thirds representative majority within one month of notification,
AND DISSENTERS WILL BE PECKED TO SUBMISSION!