3 ms·
The succession plan is "you want it to keep going, you maintain a fork"; at worst. Requiring something more to your tastes (or other demands on the governance s
by h2odragon 3y ago
The succession plan is "you want it to keep going, you maintain a fork"; at worst. Requiring something more to your tastes (or other demands on the governance style) seems to be asking a bit much. If you want "this project but run differently" then the open source license is there to give you the freedom to run your version that way.
- bruce511 3y agoYou are not wrong, the code can be forked, and it just continues. Ideally, of course, there will be just one fork not multiple people competing to be the next top dog. Other aspects of the product are somewhat harder. Things like forums, mailing lists, trademarks, graphics, logos, websites, domains and so on all form part of the "whole" and these are less-easy, or impossible, to duplicate. So yes, if you are a object owner, there are advantages to having others with "keys to the kingdom". Of course this comes with risks, so at the least a nominated successor and instructions on how to get them control of the various assets. I've been tangentially involved with cases like this, and in non-income cases spouses have generally been helpful - they like the idea of the project being kept alive. Having a plan is a big part of continuity, and I encourage solo developers, and project leads, to build and publicise the plan.