he/him 
Your assumption here is that the projects are deeply impacted by the structural changes of these foundations. Ideally, they aren't. I can only speak well to the Node.js Foundation structure, but the project has a great degree of autonomy from the Foundation.
When I was working on @babeljs, the jQuery Foundation were interested in taking on the project. Then it became the JS Foundation, and now the Node.js Foundation...? I wouldn't feel very good as a project participant with being thrown around like that.
-
-
-
Don't get me wrong, I'm happy about the announcement and trust the Node Foundation way more than any other. I'm just wondering how the project maintainers feel. Their projects are legally owned by the foundation, right? Any foundation merging means a transfer for legal ownership?
- 8 more replies
New conversation -
-
-
How come? All they're really doing is changing the name. They do the same thing: fostering OSS projects.
-
FWIW, anyone that was involved in the transition from jQuery Foundation to JS Foundation knows that it was way more than just a name change. Policies changed, the board changed, the CLA changed, events stopped being hosted, the individual membership program was dropped, etc.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.