Changes between Version 16 and Version 17 of ApertureLicense


Ignore:
Timestamp:
10/10/05 21:46:28 (19 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ApertureLicense

    v16 v17  
    1717'''Reciprocal license''' - improvements to our work (politically correct: work performed by the community) should be given back to that community. 
    1818 
    19 '''Limited reciprocity''' - on the other hand, if you create your own components that are to be placed inside the framework, e.g. an Extractor for a proprietary document format, you should not be required to make this available to the community. Rationale: this code may necessarily contain trade secrets and you don't want to scare away such users. Also, people seem to have a natural tendency for more generically applicable component to make them available to the project team, if only because they get free expert feedback and, once incorporated into the project, free code maintainance. 
     19'''Limited reciprocity''' - on the other hand, if you create your own components that are to be placed inside the framework, e.g. an Extractor for a proprietary document format, you should not be required to make this available to the community. Rationale: this code may necessarily contain trade secrets and you don't want to discourage such applications. Also, we're confident that people who build more generally applicable components will have a strong motivation for contributing those to the project, as this will provide them with free expert advice and, when the code is accepted, free maintenance. 
    2020 
    2121'''Built-in patent license''' - when you contribute code to the project, you automatically give people a royalty-free parent license for using that code, in case the code would otherwise infringe one of your patents. This prevents contributors from contributing code and coming back later to collect royalties. This patent license should be formulated in a fair way, e.g. should cover both Aperture and derivative works.