he/him 
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.
-
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.
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?
-
-
Trademark's and other property (domains) are owned by the Foundation. Copyright is not, it's owned by the contributors. and governance belongs to the projects, usually with a charter in the bylaws or passed immediately by the board after formation. Maintainers own projects.
-
JS Foundation projects seem to own the copyright? https://github.com/webpack/webpack/blob/master/LICENSE#L1 …https://github.com/lodash/lodash/blob/master/LICENSE#L3 …
- 6 more replies
New conversation -
-
-
Generally speaking, the mood about this among most the Node.js contributors I've talked to about this is largely ambivalent ... With a feeling that if it's going to move forward, it will do so regardless of how they feel about it one way or the other...
-
... so long as the daily project governance is not impacted, it's largely a non-issue. The biggest impact will likely be around marketing, the website, and infrastructure costs. We'll see tho...
- 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.