While this is an expected development, I wonder if this isn’t another opportunity being missed? Specifically, the tighter grip on Substrate.
Substrate maintenance is has mostly explicit visible costs, and mostly implicit invisible benefits. Hence, almost everyone reflexively sees Substrate as a net burden - compare the push-back that greeted the crippling strike with what now greets the coup de grâce:
Given that there are several networks that now build on Substrate, perhaps the more effective way to reduce the maintenance costs of Substrate is to free it rather than consume it?
The first step would be to further distance Substrate from Parity/W3F/Polkadot. This precludes those networks from construing any approach as an effort to have them subsidise Parity/W3F/Polkadot. How is this best done? An new foundation is overkill. But a new Github org and branding seems sufficient: open-web3-stack · GitHub
That being done (unless the admins there object), the next step remains: This is for Polkadot and Kusama to each establish a model/pattern of conduct they’d like the other networks to emulate. This can be as simple as establishing a fellowship position dedicated to the org, initially PT, and a Treasury monthly budget for docs, tutorials, issue curation, triage etc. The Fellow’s initial task is to ensure the budget is spent - hint: beggar-thy-neighbor does not lead to more people thinking “Ok, that sounds like it is worth my time”… when you have multiple people wanting to work on something you’ll find what they offer to do improves.
Those two steps are obviously in the opposite direction of where you’re currently intended to head. But they are simple, and signal to the other networks there is neutral ground - kinda like the Linux kernel is to distro’s.
Related: