package-compliant vs @pkgjs/support

[dominykas]

I figure @pkgjs/support is the "official" thing that supersedes package-compliant? Should we archive and deprecate one of those? Or possibly make one last release to call one from the other?

cc @Eomm

[Eomm]

Yes, absolutely!

I would just:

• add a warning on the readme
• add a deprecation warning to the new release with the message to prefer @pkgjs/support

(Right now, I and the nodejs-foundation npm users have publish grant)

[wesleytodd]

(Right now, I and the nodejs-foundation npm users have publish grant)

We should probably add this to all the pkgjs npm packages as well, right?

[Eomm]

(Right now, I and the nodejs-foundation npm users have publish grant)

We should probably add this to all the pkgjs npm packages as well, right?

I agree: are you suggesting to move the repo too?

Regarding the permissions on the package which org name should I invite? is it @pkgjs?

[dominykas]

Agreed actions:

• Archive the repo in the nodejs org
• Publish one last version, which instead just requires @pkgjs/support (and executes it, etc) - not sure if it has enough usage to warrant the extra effort here?)
• Deprecate the package on npm with a reference to @pkgjs/support