James M Snell

Results 791 comments of James M Snell

@anonrig ... do not bother reviewing this PR. I'm in the process of splitting it into multiple other PRs since we cannot land the bulk of these changes without autogate(s).

moving this to draft. there's a few bits to fix up but it's a low priority, will work on it as time allows.

-1. We already allow all contributors to list an individual sponsor link in the nodejs/node readme. Given that, I don't really think this additional page is worthwhile. ![image](https://github.com/user-attachments/assets/81e3ade0-0b3b-484e-91ba-8f6cb76a8eed)

As discussed in my comment https://github.com/nodejs/TSC/issues/1747#issuecomment-3049460233, I remain unconvinced this adds any actual value.

Yes, I don't think this page adds value and promotes the wrong incentives and won't carry any actual value to the project.

Just closing the loop here... here's an alternative proposed approach: https://github.com/nodejs/TSC/issues/1747#issuecomment-3092423225

Might be good to add this as a step in the v8.md/v8-updates.md docs in both this and the internal repo as a reminder

to address the CI failure here: https://github.com/cloudflare/workerd/pull/5635

If you rebase from `main` you'll pick up the CI fix.

> ... Can these expenses be adjusted to allow more money for Node.js? We have no oversight or say in what funds the Foundation may or may not make available...