Workshopper repositories refresh and publish access

[Flet]

Hi Folks!

@feross and I were chatting, and we'd like to work to help refresh the workshopper repositories to resolve the security vulnerabilities and ensure everything works on modern versions of node.

In order to do this successfully, we'll need to be able to publish new versions. Unfortunately each package has a different array of publishers on npm, which makes this challenging since so much time has passed.

is it possible to:

A. Give @feross and/or @Flet npm publish access to the workshopper packages?

B. Be added to the @workshopper npm org? I assume someone here registered it? :) We can then republish updated versions of these repositories under a single org (and wrangle npm publish access).

I'd love to help keep these tools alive as they are still valuable! I think if we take a little time to empower some folks who are interested in contributing we can keep things moving.

Anyone have thoughts on this?

@workshopper @workshopper/core @workshopper/deploy @julianduque @martinheidegger

[feross]

@julianduque just gave me npm access to javascripting and I just added you @Flet

But the rest of this issue still stands 😃

[rvagg]

Not sure who registered it but it's got me, Martin, Julián and Finn in it. I've invited you both to it.

I probably have publish access to a lot of the packages, let me know which ones you want and I can add you. +1 on getting these things sorted out and I trust you both enough that I'm happy being pretty liberal with access.

[rvagg]

fwiw there's also a @nodeschool org with the same list of members and no packages.

[feross]

@rvagg Thanks for adding us to the @workshopper org. A few requests:

• Can you add me to the learnyounode package? npm owner add feross learnyounode
• Can you make me a @workshopper owner instead of just a member? The page to do that is here: https://www.npmjs.com/settings/workshopper/members (I need that to create a team, which is required before I can grant the npm organization access to any packages.)

[feross]

I have some changes I'd like to publish now: workshopper/learnyounode#681

[rvagg]

@feross done

[ralphtheninja]

Excellent idea! Let me know if I can help out in any way.

[feross]

Okay – here's an update:

• There's now a team called developers in the npm @workshopper org. This team should contain everyone in the org. When adding new org members, remember to add them to this team.

• I granted access to the learnyounode and javascripting packages to members of the developers team.

• Anyone who has npm publish access on a workshopper can share access with the whole developers team by visiting the developers team page, typing in the package name, and clicking "Add Existing Package". Here's what it looks like:

[a0viedo]

+1 on all, let me know if you need any permissions from the @nodeschool org

[julianduque]

Excellent work Feross, that's wonderful! I can also help with permissions if needed

…

On Thu, Sep 12, 2019, 8:09 PM Alejandro Oviedo ***@***.***> wrote: +1 on all, let me know if you need any permissions from the @nodeschool <https://github.com/nodeschool> org — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#51?email_source=notifications&email_token=AAFTFNKCUKO4GTOI7D4G5WLQJLK4HA5CNFSM4IV2NIUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6TTNPI#issuecomment-531052221>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFTFNOQMNKDQZO67LZJPMDQJLK4HANCNFSM4IV2NIUA> .