I am happy to put up the repository name to a vote. Here are the choices and reasoning as I see it.. 1) github.com/apache/sling-slingpackager - short and filterable by sling- as project 2) github.com/apache/sling-js-slingpackager - the same as 1) but includes js to id it as a js project 3) github.com/apache/apache-sling-js-slingpackager - maps to npm org. I think this is better for compliance. But I am not sure. 4) github.com/apache/sling-apache-sling-js-slingpackager - also maps to npm org but starts with sling- to follow sling project conventions.
Also, can we move it to a new repo 1st and then figure out npm release? These are 2 separate issues I think (unless compliance effects repository name). I can work on any other changes required to ensure release compliance once we figure it out.
