In the slack channel there are the raw notes written down by @craftninja 👏 , during the OpenJS Summit.

The main feedback we get is that the support field in our draft could be more attractive if not included in the package.json.

The reasons pointed out are:

• it affects parsing (micro) performance for new ejs module
• what should be the semver change for this kind of addition?
• if there is a licence in package.json and LICENCE file, the last one wins
• the support changes across versions, but if I use an older version of the module, what is the support field?
• if a package is abandoned the module need to be released?

So the suggestions received are:

• Github support SUPPORT.md
• Wouldn't support have the same "signal" as a license separate JSON for support?
• How do we create solutions that are language agnostic? Could we do something that has that "signal" like a license?
• we could approach the OSI about this, think about a bigger scale, package.json could limit our ability to scale
• tidelift is doing something like this?

Let's reinvent our draft support in a best solution ✌

(I will post my thought in a separate post)