WG Supported Packages/Tools

This has come up a few times, so I figured it is the right time to raise a separate issue (#192 & #236).

How do we want to maintain our own recommended solutions? Do we want "WG supported packages"? Do we just want them in the nodejs org on github? Are we alright just letting them live under the person who wrote the best (sadly often first mover biased) solution?

I setup a GH Org and registered the corresponding npm scope pkgjs because I wanted to start working on concrete implementations of the ideas we were discussing. I am happy to offer that up to the group as an option, but I recognize that there are also downsides to a "random" named GH org/scope.

The upsides I have so far is the ability to build things quickly and get them out there. Which we might not have as easily if it was all in the node org. I also personally like the idea of a scope dedicated to JS package maintainers and tools to make it all easier.

Anyone else have thoughts on this?

Review related issues #192 and #236, then examine the proposed pkgjs GitHub organization and npm scope. Compare the options for maintaining recommended packages and tools, and document a group decision about ownership, naming, and where supported solutions should live.