Cross-License Collaborative Agreement
These terms enable contributors working together on a project covered by copyrights or patents to make collective decisions about licensing their project as a whole.
In order to get any license under these terms, you must apply to become a contributor, be accepted, and agree to these terms. These terms are both strict obligations under an agreement among all contributors and conditions to all the cross-licenses they give and receive under that agreement.
Only candidates offering contributions of copyrights or patent rights to the project can apply to become contributors.
To apply to become a contributor, a candidate must provide the following to an existing contributor:
their address for communication
their instructions for payment
a World Wide Web or other Internet address where contributors can review the contribution they are offering
For a candidate to become a contributor, an existing contributor must secure majority approval in favor of their application and circulate a current list of all contributor addresses and payment instructions. When soliciting votes for an application, the soliciting contributor must circulate the candidate’s complete application.
Any contributor may resign at any time by circulating a message of resignation. When a contributor resigns, all cross-licenses to that contributor end, but their cross-licenses to other contributors, as well as any sublicenses they have given, continue.
Each contributor gives a cross-license covering all copyrights in their contributions to the project to each other contributor.
Each contributor gives a cross-license for the project covering any patent claims they can license or become able to license to each other contributor.
Each cross-license under these terms covers all contributors, past, present, and future, and all contributions submitted to the project, past, present, and future.
Cross-licenses under these terms do not give contributors themselves any special permission for the project, only permission to give sublicenses to others.
Any contributor may give a sublicense within thirty calendar days of securing majority approval. When soliciting votes for a sublicense, a contributor must circulate:
identification of the contributor proposing to give the sublicense
an exact copy of all the proposed sublicense terms
identification of the recipient or recipients of the sublicense
a description of any relationship between those who will receive or benefit from the sublicense
an exact copy of all the terms of any agreement that has, will, or could pay the contributor proposing to give the sublicense for proposing or securing approval for the sublicense
Contributors may give sublicenses to specific recipients, categories of recipients, or the public as a whole. Sublicenses may allow sublicensing in turn. Sublicenses must apply from the time the sublicense is given, or from a time stated in the terms, not retroactively.
Each contributor is entitled to receive each message sent to any other contributor under these terms.
To circulate a message under these terms, a contributor must send the message in the English language to each other contributor, retrying as necessary.
Any contributor who receives a notice under the terms of a sublicense must circulate that notice, retrying as necessary.
The first two contributors must agree on a global, free or low-cost, high-speed, electronic communication system, such as e-mail, and provide addresses for that system. Later contributors must provide addresses for the same system.
Change of Address
Any contributor may change their address by circulating their new address from their current address. Alternatively, any contributor may change their address by circulating their new address from a different address and securing supermajority approval, without any opposing message from their old address.
Each contributor is entitled to cast a single, equal vote on each proposal under these terms.
For majority approval, a majority of responding contributors must vote in favor.
For supermajority approval, two thirds of responding contributors must vote in favor.
The contributor soliciting approval counts as a contributor voting in favor.
The deadline for approval of any proposal is thirty calendar days from when votes were first solicited.
To secure an approval, a contributor must solicit votes, then tally votes, and finally report the result.
To solicit votes, a contributor must circulate a single message with all of these details:
the identity of the project
the complete text of the proposal
the voting standard required
the date of the deadline
Contributors may vote by replying to a message soliciting votes using the same communication system. Messages like “I approve.”, “I vote in favor.”, and “Aye” count as votes in favor. Messages like “I oppose.”, “I vote against.”, and “Nay” count as votes against.
To tally votes, the contributor who solicited votes must ensure that each vote message is circulated. If the communication system enables forwarding messages verbatim, such as by forwarding e-mail, the contributor must forward vote messages verbatim. If a voting contributor circulates their vote themself, the contributor soliciting votes need not circulate it again.
To report a result, the contributor who solicited votes must circulate a single message with all of these details within seven calendar days after the deadline:
all the information required to solicit votes
copies of all vote messages
counts of votes in favor, votes against, and contributors not responding by the deadline
whether contributors approved the proposal or not
Each contributor is entitled to receive an equal share of license fees, license royalties, and other license-based payments for the project. Any sublicense that entitles any contributor to payment must require payment to the contributor who gave the sublicense to start, and to any successor for which any contributor secures majority approval after.
Any contributor who receives payment under a sublicense must pay other contributors their equal shares of funds received within fourteen calendar days, according to their payment instructions, retrying as necessary.
Payment Processing Fees
If a contributor’s payment instructions require the distributing contributor to pay a fee, the contributor making the payment may reduce the amount of the payment by the amount of the fee, so the distributing contributor does not have to pay any processing fees out of pocket.
If a contributor does not respond to a payment of their share, the next step depends on the amount of their share.
If the amount is ten percent or less of the payment under the sublicense, or the payment processing fees would be 50% or more of the amount, then the distributing contributor may keep the amount for themself.
Otherwise, the distributing contributor must try to pay themself and other contributors, but not the contributor that is not responding, equal shares of the amount, according to their payment instructions. If those payments fail, the distributing contributor does not have to retry them, but can keep the amounts for themself.
Contributors must provide payment instructions for global, low-cost, high-speed, electronic payment systems.
Change of Payment Instructions
Any contributor may change their payment instructions by circulating new payment instructions from their current address.
When a communication or payment system fails to deliver a message or payment:
The sending contributor must circulate word of the failure and any failure message from the system.
The sending contributor must wait 48 hours, then try again. If the receiving contributor changed their address or changed their payment instructions since the first try, the sending contributor must use the new address or payment instructions.
If the second try also fails, the sending contributor must circulate word of the failure and any failure message from the system. The receiving contributor is then considered to be not responding.
Any contributor may change these terms by securing supermajority approval in favor of the change. Changes apply from the time of approval going forward, not retroactively.
As far as the law allows, the project comes as is, without any warranty or condition, and no contributor will be liable to any other contributor for any damages related to the project or these terms, under any kind of legal claim.