OSE License Requirements: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
(Created page with "Requirements #Duration - permanent protection of IP #Protection - protects users of technology, downstream users, developers, on-demand manufacturers and commercial producer...")
 
No edit summary
Line 6: Line 6:
#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
#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
#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
#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
#  
#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.
#Versioning - versions of hardware artificts must be versioned clearly, with
#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.
#Repository - official repository is held by OSE or its assigns
#New entries in repository - commits a
#Explicit allowance of commercial use, including on-demand manufacturing
#Explicit ethical stand on Distributive Enterprise - or open publishing of enterprise blueprints based on the hardware artifacts
#Specific license for producers is to be granted by OSE for those wishing to use the OSE trademark - similar to Arduino model. Terms to be specified.


Documentation* - you promise to mail, provide through URL for 3 years, open file format with new and original documentation, must email out modification to all licensees
Summary of changes
New documentation in full
Original documentation in full
Original documentation in full
*OSE Documentation amendment- would requirement link to a single repository, making documentation accessible - original documentation is not necessary  
*OSE Documentation amendment- would requirement link to a single repository, making documentation accessible - original documentation is not necessary  

Revision as of 12:37, 3 September 2013

Requirements


  1. Duration - permanent protection of IP
  2. Protection - protects users of technology, downstream users, developers, on-demand manufacturers and commercial producers
  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. 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
  5. 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.
  6. Versioning - versions of hardware artificts must be versioned clearly, with
  7. 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.
  8. Repository - official repository is held by OSE or its assigns
  9. New entries in repository - commits a
  10. Explicit allowance of commercial use, including on-demand manufacturing
  11. Explicit ethical stand on Distributive Enterprise - or open publishing of enterprise blueprints based on the hardware artifacts
  12. Specific license for producers is to be granted by OSE for those wishing to use the OSE trademark - similar to Arduino model. Terms to be specified.

Original documentation in full

  • OSE Documentation amendment- would requirement link to a single repository, making documentation accessible - original documentation is not necessary

On Demand Manufacturing* (ODM) - (Skype broke up) - protect people who print on demand, reassuring them that they are protected

  • OSE’s ODM amendment - explicit allowance wrt ODM

Warranty - assures anyone who contributes will not be liable down the line Licensing - need to put “all later versions specified” otherwise anyone who remixes must keep it under the original license, so if it goes out at 1.0, if any new versions come out then they are under 1.0


CERN http://www.ohwr.org/projects/cernohl/wiki End users - firms -protects firms that may want to control the patent later Documentation - must distribute documentation, no format preference On Demand Manufacturing - CERN says nothing Warranty - assures anyone who contributes will not be liable down the line Licensing - automatic