License Requirements

Below are some considerations and guidelines for the restrictive license clauses to be developed.

Needs to detail exactly what is being Ransomed. Examples include any binary versions of software, if any plugins/modules/extras or just a core work, etc... Boilerplate words should be developed to allow easy cut/paste by Holders. Should these details be included in the restrictive license, or pointed to as a separate file (RANSOMWARE.TXT?)
The Ransom Total needed to free the Work.
Specify the Free License to be used when freed. Potential allowed licenses are any OSI/FSF/CC approved ones.
A single Ransom Payment amount from contributors to the Holder. An installment towards the Ransom Total.
The restrictive terms to be granted to the contributor. This would be an inherent part of the restrictive license. This project will probably just specify add-on clauses in a separate file.
The Expiration Date, when the Work will automatically and legally be re-licensed under the Free License specified in the Ransom Clauses.
Special Exceptions, ie: those that recieve the ransom at no cost due to non-profit status, contributions, etc... Should be at developers discretion but clearly defined in the Clauses.