# Cross-License Collaborative Agreement
Version 1.0.0-pre.1
## Purpose
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.
## Acceptance
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.
## Contributors
### Qualifications
Only candidates offering contributions of copyrights or patent rights to the project can apply to become contributors.
### Application
To apply to become a contributor, a candidate must provide the following to an existing contributor:
1. their [address](#addresses) for [communication](#communications)
2. their [instructions](#payment-instructions) for [payment](#payments)
3. a World Wide Web or other Internet address where contributors can review the contribution they are offering
### Admission
For a candidate to become a contributor, an existing contributor must secure [majority approval](#majority) in favor of their application. When [soliciting votes](#soliciting-votes) for an application, the soliciting contributor must [circulate](#circulating-messages) the candidate's complete [application](#application).
### Resignation
Any contributor may resign at any time by [circulating](#circulating-messages) 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.
## Cross-Licenses
### Copyright
Each contributor gives a cross-license covering all copyrights in their contributions to the project to each other contributor.
### Patent
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.
### Scope
Each cross-license under these terms covers all contributors, past, present, and future, and all contributions submitted to the project, past, present, and future.
### Rights
Cross-licenses under these terms do not give contributors themselves any special permission for the project, only permission to give sublicenses to others.
### Sublicensing
Any contributor may give a sublicense within thirty calendar days of securing [majority approval](#majority). When [soliciting votes](#soliciting-votes) for a sublicense, a contributor must [circulate](#circulating-messages):
1. identification of the contributor proposing to give the sublicense
2. an exact copy of all the proposed sublicense terms
3. identification of the recipient or recipients of the sublicense
4. a description of any relationship between with those who will receive or benefit from the sublicense
5. 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, a 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.
## Communications
### Equal Information
Each contributor is entitled to an opportunity to receive each message sent to any other contributor under these terms.
### Circulating Messages
To circulate a message under these terms, a contributor must send the message in the English language to each other contributor, [retrying](#retry) as necessary.
### Circulating Notices
Any contributor who receives a notice under a sublicense must [circulate](#circulating-messages) that notice, [retrying](#retrying) as necessary.
### Addresses
The first and second 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](#circulating-messages) their new address from their current address. Alternatively, any contributor may change their address by [circulating](#circulating-messages) their new address from a different address and securing [supermajority approval](#supermajority), without any opposing message from the address to be replaced.
## Voting
### Equal Vote
Each contributor is entitled to an opportunity to cast a single, equal vote on each proposal under these terms.
### Majority
For majority approval, a majority of responding contributors must vote in favor.
### Supermajority
For supermajority approval, two thirds of responding contributors must vote in favor.
### Counting
The contributor soliciting approval counts as a contributor voting in favor.
### Deadline
The deadline for approval of any proposal is thirty calendar days from when [votes were first solicited](#soliciting-votes).
### Securing Approval
To secure an approval, a contributor must [solicit votes](#soliciting-votes), then [tally votes](#tallying-votes), and finally [report the result](#reporting-results).
### Soliciting Votes
To solicit votes, a contributor must [circulate](#circulating-messages) a single message with all of these details:
1. the identity of the project
2. the complete text of the proposal
3. the voting standard required
4. the [deadline](#deadline)
### Casting Votes
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" indicate a vote in favor. Messages like "I oppose.", "I vote against.", and "Nay" indicate a vote against.
### Tallying Votes
To tally votes, the contributor who solicited votes must ensure that each vote message is [circulated](#circulating-messages). 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](#circulating-messages) their vote themself, the contributor soliciting votes does not have to [circulate](#circulating-messages) it again.
### Reporting Results
To report a result, the contributor who solicited votes must [circulate](#circulating-messages) a single message with all of these details within seven calendar days after the [deadline](#deadline):
1. all the information required to [solicit votes](#soliciting-votes)
2. copies of all [vote messages](#voting)
3. counts of votes in favor, votes against, and contributors not responding by the [deadline](#deadline)
4. whether contributors approved the proposal or not
## Payments
### Equal Pay
Each contributor is entitled to an opportunity to receive an equal share of license fees 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](#majority) after.
### Distributing Payments
Any contributor who receives payment under a sublicense must pay other contributors their [equal shares](#equal-pay) of funds received within fourteen calendar days, according to their [payment instructions](#payment-instructions), [retrying](#retry) as necessary.
### Payment Processing Fees
If a contributor's [payment instructions](#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.
### Failed Payments
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 equal shares of the amount, according to their [payment instructions](#payment-instructions). The distributing contributor does not have to [retry](#retry) failed payments. They can keep failed payments for themself.
### Payment Instructions
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](#payment-instructions) by [circulating](#circulating-messages) new [payment instructions](#payment-instructions) from their current [address](#addresses).
## Retry
When a [communication](#communications) or [payment](#payments) system fails to deliver a message or payment:
1. The sending contributor must [circulate](#circulating-messages) word of the failure and any failure message from the system.
2. The sending contributor must wait 48 hours, then try again. If the receiving contributor [changed](#change-of-address) their [address](#address) or [changed](#change-of-payment-instructions) their [payment instructions](#payment-instructions) since the first try, the sending contributor must use the new [address](#address) or [payment instructions](#payment-instructions).
3. If the second try also fails, the sending contributor must [circulate](#circulating-messages) word of the failure and any failure message from the system. The receiving contributor is then considered to be not responding.
## Changes
Any contributor may change these terms by securing [supermajority approval](#supermajority) in favor of the change. Changes apply from the time of approval going forward, not retroactively.
## No Liability
***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.***