terrain_aggregator licensing policy

[dhardestylewis]

terrain_aggregator licensing policy

In keeping with the spirit of :

• maximizing open-source development,
• while meeting existing source-code development practice in government and engineering,
• and encouraging adoption of open-source development practices

The licensing policy for this work is :

• copyleft licenses for all aspects of code development including code, data, documentation while the code & data is under development & review. These licenses have been established as :
  • GPL (v3+) for code
  • GFDL (v1.3+) for documentation
  • OdbL (v1.0+) for databases
  • DbCL (v1.0+) for data
  • CC-BY-SA (v4.0+) dual license for documentation & data
• more permissive licenses for data once it has been more thoroughly QAQCed. These licenses will be:
  • ODC-By (v1.0+) for databases
  • CC-BY (v4.0+) for data
• code may also see more permissive licensing as relationships develop and use-cases or partnerships are identified. In which case the license will be:
  • Apache (v2.0+) for code

Goals of this dual-licensing approach:

• enable an open-source environment for entities producing tiles
• leaving open the door to collaborations with those interested in :
  • helping develop tiles,
  • advocate for the development of tiles, or
  • using the tiles
• encourage adoption of open-source practices for those wanting to work with the most bleeding-edge code & data,
• while providing the choice to wait until more permissively licensed data is available

In practice,

• the license for each tile is tracked individually in the single_seamless_elevation DB

There are two releases of single_seamless_elevation :

• the bleeding-edge release has tiles tagged
  • DbCL or CC-BY-SA if they are still in QAQC, or
  • CC-BY if they are already released for production use
• the stable release has all tiles tagged
  • CC-BY

Because we anticipate single_seamless_elevation will be used as an upstream data source for many engineers & consultancies, any open-source license protects upstream data providers by with standard clauses that :

• limit liability, and
• disclaim warranty
  (It is important that any licensing include these clauses in order to ensure that use of this data by downstream engineers does not result in litigation for developers of this data.)

[darctur]

Hi Daniel, just letting you know I’m on vacation till Aug 1. I won’t be able to look at this till then. dka +1-512-771-1434

…

Sent from my iPhone On Jul 22, 2022, at 7:27 PM, Daniel Hardesty Lewis ***@***.***> wrote:  TNRIS Lidar retiling licensing policy In keeping with the spirit of : maximizing open-source development, while meeting existing state-agency source-code development practices, and enabling "behavior change" of state agency's source code development practices The licensing policy for this work is : copyleft licenses for all aspects of code development including code, data, documentation while the code & data is under development & review. These licenses have been established as : GPL (v3+) for code GFDL (v1.3+) for documentation OdbL (v1.0+) for databases DbCL (v1.0+) for data CC-BY-SA (v4.0+) dual license for documentation & data more permissive licenses for data once it has been more thoroughly QAQCed. These licenses will be: ODC-By (v1.0+) for databases CC-BY (v4.0+) for data code may also see more permissive licensing as relationships develop and use-cases or partnerships are identified. In which case the license will be: Apache (v2.0+) for code Goals of this dual-licensing approach: enable an open-source environment for entities producing tiles leaving open the door to collaborations with those interested in : helping develop tiles, advocate for the development of tiles, or using the tiles encourage adoption of open-source practices for those wanting to work with the most bleeding-edge code & data, while providing the choice to wait until more permissively licensed data is available In practice, the license for each tile is tracked individually in the single_seamless_elevation DB There are two releases of single_seamless_elevation : the bleeding-edge release has tiles tagged DbCL or CC-BY-SA if they are still in QAQC, or CC-BY if they are already released for production use the stable release has all tiles tagged CC-BY Because we anticipate single_seamless_elevation will be used as an upstream data source for many engineers & consultancies, any open-source license protects upstream data providers by with standard clauses that : limit liability, and disclaim warranty (It is important that any licensing include these clauses in order to ensure that use of this data by downstream engineers does not result in litigation for developers of this data.) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were assigned.