New ask Hacker News story: Ask HN: Delayed open source licensing / “eventually open” examples?
Ask HN: Delayed open source licensing / “eventually open” examples?
3 by schoen | 2 comments on Hacker News.
Hi! I'm working on a project with the Open Source Initiative and Open Tech Strategies which is collecting historical examples of "delayed open source licensing". This refers to licensing of software projects that were not initially free/open source when released, but became so on a (pre-planned and pre-announced) delay. For instance, a software developer might initially publish a project as proprietary or "open core" but announce that improvements will be relicensed Apache or GPL with a 1 or 2-year delay. There are dozens of projects that have pursued versions of this licensing strategy and several different license texts used to implement it (such as the Transitive Grace Period Public License/Bootstrap Open Source License, and the Business Source License). Can you help us identify more? You can see ones that we know about already at https://ift.tt/gOyvhbs You can post examples (projects or licenses) here, or e-mail to dosp-research at the Open Source Initiative's domain name. You can also see Karl Fogel's request at https://ift.tt/fWz2GeA Note: We're not looking for examples of initially-proprietary projects that were permanently relicensed as a result of a one-time decision that wasn't planned or announced ahead of time. For example, Netscape Navigator -> Firefox doesn't count because Netscape didn't originally have a plan to make it open source. By default, we'll publicly credit you for your suggestion when we eventually publish a whitepaper collecting these examples. Thanks!
3 by schoen | 2 comments on Hacker News.
Hi! I'm working on a project with the Open Source Initiative and Open Tech Strategies which is collecting historical examples of "delayed open source licensing". This refers to licensing of software projects that were not initially free/open source when released, but became so on a (pre-planned and pre-announced) delay. For instance, a software developer might initially publish a project as proprietary or "open core" but announce that improvements will be relicensed Apache or GPL with a 1 or 2-year delay. There are dozens of projects that have pursued versions of this licensing strategy and several different license texts used to implement it (such as the Transitive Grace Period Public License/Bootstrap Open Source License, and the Business Source License). Can you help us identify more? You can see ones that we know about already at https://ift.tt/gOyvhbs You can post examples (projects or licenses) here, or e-mail to dosp-research at the Open Source Initiative's domain name. You can also see Karl Fogel's request at https://ift.tt/fWz2GeA Note: We're not looking for examples of initially-proprietary projects that were permanently relicensed as a result of a one-time decision that wasn't planned or announced ahead of time. For example, Netscape Navigator -> Firefox doesn't count because Netscape didn't originally have a plan to make it open source. By default, we'll publicly credit you for your suggestion when we eventually publish a whitepaper collecting these examples. Thanks!
Comments
Post a Comment