I will follow up by e-mail shortly, but can't help adding a couple things to two lines of thought in your response:
Here's an open form agreement that I wrote from scratch for contractors that allows switching from terms for "open" and more traditionally "closed" projects: https://github.com/kemitchell/switchmode Terms for either "mode" are compatible with use of OSS and collaboration with OSS communities.
I represent both open-style devs doing paid work and companies who hire them. I tried to strike a balance, in much more approachable language, with Switchmode.
L0 currently supports one kind of very dramatic licensing transition: developers can offer to relicense their projects BSD-2-Clause for a stated amount. Sponsor pays the price, developer automatically grants a BSD-2-Clause license, and takes obligations to update notices and push commits accordingly.
Here's an open form agreement that I wrote from scratch for contractors that allows switching from terms for "open" and more traditionally "closed" projects: https://github.com/kemitchell/switchmode Terms for either "mode" are compatible with use of OSS and collaboration with OSS communities.
I represent both open-style devs doing paid work and companies who hire them. I tried to strike a balance, in much more approachable language, with Switchmode.
L0 currently supports one kind of very dramatic licensing transition: developers can offer to relicense their projects BSD-2-Clause for a stated amount. Sponsor pays the price, developer automatically grants a BSD-2-Clause license, and takes obligations to update notices and push commits accordingly.