|
|
|
|
|
|
by damethos
1556 days ago
|
|
|
I was about to reply something similar but your comment totally covered me. NPM had some thoughts about providing package.json metadata in order for the customers to know the author intentions but I am not sure what happened to it. I remember reading about it in this article: https://www.theregister.com/2020/10/28/nodejs_15_michael_daw... > The [module] maintainers are struggling," he said. "They may have written a module, it was a
hobby they did on a weekend, now they've got 20,000,000 downloads and the people who are
using it
> have expectations which are more than what > is appropriate for something that
they're getting for free. We've worked on something that we call package support which is
adding extra metadata to
> the package JSON, which allows the maintainer to provide information
about their intention in terms of support. So what kind of support is there? Is it best effort? Is there no support at all? Is there
> a company? Is it part of a foundation? - Michael Dawson |
|
|
The default answer is: No. There is no support. And that's written in the license already.
Announcing anything beyond that is called an ad. It may be a useful ad, but it's still an ad.
(Assuming it's paid support. If it's support "for free" then that's part of the problem if it's social-pressures somebody to do this in their free time. You are externalizing your business support costs. And you really want to build your business empire on a teenager's hobby project? So, whoever is interested in this "intention" metadata should only really care about paid support, and then that's an ad.)