Re: Publishing packages on npmjs.com

[Robert Munteanu <ro...@apache.org>]

Thanks, Ruben.

I will then create the @apache-sling org on NPM. There is only one
question left - how to manage credentials. I see two options:

1. Create a shared account that is registered using the 
'private@sling.apache.org' email. This makes sure credentials are not
tied to a single account, but then again makes it harder to revoke and
there is less tracing.

2. Create it using my account and then grant access to other PMC
members on-demand, using the '@apache.org' accounts.

I slightly prefer 2, I think the credentials are better handled without
reset links being accessible in (privately) archived mailing lists.

I plan to create the org on Monday, so if you have other ideas, please
let me know.

Thanks,
Robert


On Thu, 2019-10-24 at 05:37 -0700, Ruben Reusser wrote:
> 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
> > 

Re: Publishing packages on npmjs.com

[Ruben Reusser <rr...@headwire.com>]

Robert, I do not have an opinion on 1 or 2. Do what's best for the sling 
PMC team

Ruben

On 11/6/2019 9:11 AM, Robert Munteanu wrote:
> Thanks, Ruben.
>
> I will then create the @apache-sling org on NPM. There is only one
> question left - how to manage credentials. I see two options:
>
> 1. Create a shared account that is registered using the
> 'private@sling.apache.org' email. This makes sure credentials are not
> tied to a single account, but then again makes it harder to revoke and
> there is less tracing.
>
> 2. Create it using my account and then grant access to other PMC
> members on-demand, using the '@apache.org' accounts.
>
> I slightly prefer 2, I think the credentials are better handled without
> reset links being accessible in (privately) archived mailing lists.
>
> I plan to create the org on Monday, so if you have other ideas, please
> let me know.
>
> Thanks,
> Robert
>
>
> On Thu, 2019-10-24 at 05:37 -0700, Ruben Reusser wrote:
>> 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
>>>