-
Notifications
You must be signed in to change notification settings - Fork 1k
README needs to say Vercel does not maintain this package anymore #1600
Comments
I agree |
Who decides which pull-requests are accepted into the next version? Who decides and does publish the releases? Vercel, or the outside collaborators? |
Non vercel associated maintainers, from what I'm seeing |
I review pull requests and make technical decisions. I also make release calls. Vercel is still the steward of the project, and an authorized Vercel employee reviews and publishes the release to npm. Please read the license of the project carefully:
It is not appropriate to proclaim entitlement to free support, in any open source project. Maintainers maintain the project in a best-effort basis with good faith. Please contribute to the project with a PR if the matter is of particular urgency to you. |
No need to be oversensitive and quote the license Jesse. Nobody is demanding free support.
It's already clear Vercel doesn't maintain this project anymore. Why not be transparent about that so people can be aware of that when deciding whether this is a package they want to use? |
People who want to choose this package might think it's being maintained by Vercel but they have stopped maintaining it a long time ago. It should be moved to a different github organization or the README needs to say this so users don't think there's a company like Vercel behind it.
#262 (comment)
The text was updated successfully, but these errors were encountered: