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.
-
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 …
-
-
this approach is highly problematic and I've argued against it many times. this obviously isn't a requirement in the Node.js Foundation and we'll see how this shakes out in the merger.
-
Node.js Foundation does this way better?https://github.com/nodejs/node/blob/master/LICENSE#L4 …
- 4 more replies
New conversation -
-
-
BTW, the copyright line does not handle all assignment. Notice the "and other contributors" line, it means that the JS Foundation owns some of the copyright and other contributors own other parts (usually). the JSF has a CLA though so I'm not sure how this is structured.
-
this isn't very well understood, but the copyright notice isn't a binding assignment agreement. if I send a PR to a project without a CLA and it says "Copyright Scooby Doo" and the project accepts the PR, I still own the copyright for my contribution.
End of conversation
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.