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://code.librehq.com/ots/dosp-research/-/blob/main/notes.md
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://kfogel.org/notice/AZSlnFS0GBe2x7Rd6u
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!
edit: I see North Road is actually on your list, but eventual openness not obvious. I think that's clear for SLYR at least.
Atom had a delayed open sourcing but I don't know if this was planned, they had already open sourced some parts of it but not the whole editor: https://atom-editor.cc/blog/2014/05/06/atom-is-now-open-sour...
Same with Ghostty: https://mitchellh.com/ghostty