L0 says nothing about revenue sharing or other financial arrangements of more than one player. L0's CLI _does_ support "stacking" metadata about available priv

L0 says nothing about revenue sharing or other financial arrangements of more than one player. L0's CLI _does_ support "stacking" metadata about available private licenses. So if you start an L0-NC project, I fork it and add my own significant contributions, folks who download my fork can tell they need private terms from both of us, at the prices we set independently. I suspect many small projects, which are effectively single-maintainer, many-contributor, will accept contributions BSD-2-Clause, or offer waivers (essentially freebie private licenses) for the project in return for contributions on BSD-2-Clause terms. There's some exciting work being done by others on transparent, automated licensing and royalties. As an aside, I think that line of research is far more promising for the kind of "network team", "swarm of contractors" business aspiration than models tackling, say, equity stakes or 701 plans. But it's not directly in scope for L0.