Robert, thank you for looking into this
there is also a sling-packager user package preventing us from using
sling-packager or slingpackager.
I honestly would prefer the org and as an org only 1 is an option.
thank you
Ruben
On 10/24/2019 3:04 AM, Robert Munteanu wrote:
Hi,
In https://issues.apache.org/jira/browse/SLING-8747 we are discussing
how to publish Sling packages on npmjs.com .
First thing to settle would be the naming convention. I guess we have
four options here:
1. @apache-sling/$PACKAGE-NAME
2. @sling/$PACKAGE-NAME
3. apache-sling-$PACKAGE-NAME
4. sling-$PACKAGE-NAME
I think an org is preferrable since we would be able to add multiple
accounts to it.
There already is a user package https://www.npmjs.com/package/sling ,
so I'm not sure if we can create a @sling organisation.
Which option to you prefer? New ones are welcome, of course.
Thanks,
Robert
