January 2020 License-Discuss Summary

License-Discuss mailing list topics for January 2020:

  • Dual Licensing
  • Copyright on APIs
  • Decision process regarding license review submissions
  • AGPL evaluation and real-world license testing
  • ZFS Kernel Code on Linux

Dual Licensing
https://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/2020-January/021191.html

Centralizing copyright licensing and not centralizing copyrights themselves 
https://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/2020-January/021192.html

Single entity open source business model
https://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/2020-January/021204.html

Copyright on APIs
https://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/2020-January/021193.html

Doubt on article assumptions due to machine-readable interface description in the source code
https://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/2020-January/021194.html

Decision process regarding license review submissions
https://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/2020-January/021195.html

Suggestion to postpone OSI evaluation of new licenses until after some time of practical use
https://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/2020-January/021199.html

The role of the OSI and defining norms
https://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/2020-January/021201.html

Writing down all rules would be divisive and further enable bad actors 
https://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/2020-January/021207.html

Postponing evaluation means ignoring and that the current OSI certification process is fine and shouldn’t be changed because of one license being reviewed. Introduce retiring licenses or have a category of "open source but not recommended."
https://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/2020-January/021203.html

It is undesirable to have the OSI determine which licenses are better than others
https://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/2020-January/021208.html

Concern with interim naming of a license while it is in use but before OSI evaluation
https://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/2020-January/021212.html

AGPL evaluation and real-world license testing
https://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/2020-January/021197.html

Copyleft-next is engaging in a public drafting process
https://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/2020-January/021198.html

ZFS Kernel Code on Linux
https://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/2020-January/021215.html
 

To promote and protect open source software and communities...

For over 20 years the Open Source Initiative (OSI) has worked to raise awareness and adoption of open source software, and build bridges between open source communities of practice. As a global non-profit, the OSI champions software freedom in society through education, collaboration, and infrastructure, stewarding the Open Source Definition (OSD), and preventing abuse of the ideals and ethos inherent to the open source movement.

Open source software is made by many people and distributed under an OSD-compliant license which grants all the rights to use, study, change, and share the software in modified and unmodified form. Software freedom is essential to enabling community development of open source software.