If I did start an open source project, I think I would do a very simple licensing that I have never encountered, like: "Dual licensing: Paid software now, and G

If I did start an open source project, I think I would do a very simple licensing that I have never encountered, like: "Dual licensing: Paid software now, and GPL starting 2032". I guess in the oss monetization list it is covered by "paid early access: Delayed open-sourcing". The software source code is released day one, but it won't be a FOSS license until YEAR+N. The license switch will be automatic after the deadline. That way I think I can have the best of both worlds: making sure development is paid (which is often necessary to sustain any large project) and any additional valuable development being be paid for, but also giving your customers the guarantee that they'll have an exit against vendor lock-in, and releasing in the long term to the FOSS community. Basically I sell software normally, but commit to a future FOSS license at the same time. It's not unlike patents actually, at least what they should be.