-
Notifications
You must be signed in to change notification settings - Fork 146
Create a directory for funding individual contributors #981
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Create a directory for funding individual contributors #981
Conversation
Signed-off-by: Darshan Sen <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Making the -1 explicit. See my other comment for reasoning.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
provides an easy to consume (for the sponsors) mapping of topics / skills and people. this can improve sponsorship.
I agree with Gireesh. @jasnell I have responded to your comment in the original issue nodejs/TSC#1747 (comment) |
I have concerns about the maintainability of such list, with time goes on and contributors come and go, and/or change their areas of interest, I'd expect the table to quickly become outdated, hurting its relevance. We'd need some process to at least removing contributors who are no longer active – if that's restricted to Node.js Collaborators, it could be done when moving to emeritus, although I'm not sure adding more friction to that process is something we actually want. |
Changes in interests should be updated manually by contributors. |
As discussed in my comment nodejs/TSC#1747 (comment), I remain unconvinced this adds any actual value. |
|
||
Name | Contact | Areas of interest and expertise | | ||
------------|-----------------------|---------------------------------| | ||
Darshan Sen | <[email protected]> | Single executable applications | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aside from my general objection that I don't think this page adds value and shouldn't land at all, if that objection is overruled and it does land then it should be populated with details for all of the maintainers with "Sponsor Me" links on the nodejs/node README rather than just having a single entry before it lands. Also, the table should have the links to the individual's "Sponsor Me" page rather than the email link.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with @jasnell—this page should either be expanded to include all maintainers with public “Sponsor Me” links (not just one), and those links should be direct to sponsor platforms, not emails.
If there isn’t sufficient interest or consensus, it might be better to close this PR for now.
@jasnell I have responded in nodejs/TSC#1747 (comment). Are you still blocking? |
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: nodejs/TSC#1747 (comment) |
This is a follow-up of nodejs/TSC#1747.
This creates a directory of maintainers who are open to receive funding. The goal is to provide visibility and a simple way for users and organizations to support individual maintainers directly.
The initial version of the list includes just myself, with the structure in place for others to be added as they opt in.
cc @nodejs/tsc