[
https://issues.apache.org/jira/browse/SLING-8747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16958732#comment-16958732
]
Robert Munteanu commented on SLING-8747:
----------------------------------------
So I guess we have four options here:
- @apache-sling/$PACKAGE-NAME
- @sling/$PACKAGE-NAME
- apache-sling-$PACKAGE-NAME
- sling-$PACKAGE-NAME
There already is a user package https://www.npmjs.com/package/sling , so I'm
not sure if we can create a @sling org. I would be inclined to go with
@apache-sling/$PACKAGE-NAME . I will discuss this on dev@sling
> establish @apachesling npmjs organization
> -----------------------------------------
>
> Key: SLING-8747
> URL: https://issues.apache.org/jira/browse/SLING-8747
> Project: Sling
> Issue Type: Improvement
> Components: CI
> Reporter: Ruben Reusser
> Priority: Major
>
> now that the donation for the slingpackager has been accepted we need to
> create a common apachesling organization on npmjs and start setting up a
> ci/cd flow to release the slingpackager
> https://issues.apache.org/jira/browse/SLING-8584
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
