NPM publish maintainers

[rborn]

We should have 2 maintainers + backup that are allowed to publish on npm.

There are cases where the modules have only one maintainer with rights and this can become a bottleneck when he or she is not able to push.

[grabbou]

Hm, right now, there are few global organisation-wise admins - isn't this enough for the "backup"?

I think having the teams that have explicit list of projects is also important to avoid assigning organisation-wide permissions by accident to some people.

[rborn]

The problem is that sometimes there is a bottleneck in publishing to npm.
There were cases when some urgent fixed bugs were not pushed becauase the person with the permissions wasn't available.

[kelset]

few global organisation-wise admins

I feel that we should have a more granular approach to this, like, every maintainer should have only npm publish auth for his/her project. My understanding is that at the moment it's not that way, correct?

CC @Titozzz

[grabbou]

I think that's exactly how it's set up except for me, Tittoz and Christoph (but I might be wrong).

…

On Tue, 7 May 2019 at 15:05, Lorenzo Sciandra ***@***.***> wrote: few global organisation-wise admins I feel that we should have a more granular approach to this, like, every maintainer should have only npm publish auth for his/her project. My understanding is that at the moment it's not that way, correct? CC @Titozzz <https://github.com/Titozzz> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#7 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AASZZRRLY2CLLITJ6B6YMW3PUF47ZANCNFSM4HBOBHTQ> .