OSE License Requirements

Requirements

1. Duration - permanent protection of IP
2. Protection - In general, bilateral - or both developer and user of any sort is protected. Protects users of technology, builders of technology from potential patent suit against them; downstream users, on-demand manufacturers and commercial producers. Protects developers from any issue resulting from other individuals or corporations producing the product
3. Documentation - no requirements for sending updates/emails to any developers, but just providing a link to a repository. OSE must provide a clear link to its documentation from its website
4. Standardized taxonomy is to be developed for documentation
5. Specifications for documentation - we are currently in the process of refining the specific taxonomy for all documentation content in 2 categories: (1) absolutely mandatory content that any OSE-Licensed product must have to assure full replicability of a hardware artifact; (2) nice-to-have content that assists in continued development, but is not necessary to the replication per se
6. Amendment of License - license is versioned, and any product using license must display specific license version. License may be amended by OSE according to a specific protocol, to be defined.
7. Versioning - versions of hardware artificts must be versioned clearly, with
8. Commits - A specific process for commits involves the Founder and 'lieutenants' equivalent of the linux model. Process to be defined specifically. Official commits are found at repository. Commit control may be assigned to specific parties as project grows.
9. Repository - official repository is held by OSE or its assigns
10. New entries in repository - commits a
11. Explicit allowance of commercial use, including on-demand manufacturing
12. Explicit ethical stand on Distributive Enterprise - or open publishing of enterprise blueprints based on the hardware artifacts
13. Specific license is needed for producers - to be granted by OSE for those wishing to use the OSE trademark - similar to Arduino model. Terms to be specified, requires payment to maintain the licensing infrastructure.
14. Licensing to others involves a quality control protocol.
15. OSE products under OSE label go through an internal and external quality control process, to be defined.
16. Any OSE-licensed product must be shipped with a clear link to documentation
17. Product warranty requires that any manufacturer provide only operations/safety/maintenance information, and it only suggests that a service infrastructure be created for products sold
18. Patents - I would like patents to be replaced with a court test case of the OSE license