Automate org invitation of new contributors in nodejs/nodejs.org

[fhemberger]

The nodejs/nodejs.org repo regularly adds new contributors as new team members. This allowed us to assemble a great, very committed team of 165 members, handling every aspect of the website including translations for thirteen languages.

So far, this has been a manual task, performed every couple of months. As a team maintainer, I can add existing Node.js org members to the website team, but it requires an org admin to onboard new members. So instead of setting up a regular reminder for myself to compile the list of new contributors and then needing to bother an admin to invite each of them manually, there's a GitHub bot that could automate the process:

https://probot.github.io/apps/invite-contributors (source)

I would require the following permissions:

Is there any way we could set it up for the website repo?

Ref: nodejs/nodejs.org#1872

[fhemberger]

/ping @bnb @mhdawson @MylesBorins

[MylesBorins]

@fhemberger I am not personally comfortable with giving a bot administration privileges. I'll not block on this if others sign off though.

[bnb]

I am fine with this. As far as I know all sensitive data (in a Security sense) has been moved out of this organization.

IMO we need to begin allowing org members to smooth out their workflow with bots. I've asked various people at least a dozen times and have been told to go somewhere else to ask, never actually getting an answer.

This bot will reduce the maintenance burden on the current active contributors (mainly @fhemberger), which we should not be stopping because we don't have a process defined and nobody is willing/able to define a process.

[refack]

We should also consider that org members get two extra privileges: access to nodejs/moderation, and free individual membership in the foundation.

I know it's a bit cumbersome, but I prefer that this decision will be done by a human.

[fhemberger]

I know it's a bit cumbersome, but I prefer that this decision will be done by a human.

Well, as I've been the only human caring about the onboarding since I took over from Mikeal, I don't want to do this job manually any longer:

1. Setup a reminder
2. Run the script, compiling the list (approx. 10-20 new contributors on each run)
3. Create an issue
4. Having to bother an admin to send out the invitations
5. Rinse and repeat every 2-3 months.

There has to be a way to improve the situation and I'd love your help with that.

[refack]

There has to be a way to improve the situation and I'd love your help with that.

Ack.

[bnb]

We should also consider that org members get two extra privileges: access to nodejs/moderation, and free individual membership in the foundation.

These aren't excessively useful benefits, especially since the people are literally contributing and these are benefits given to contributors. Since the Website WG has its own governance, it can add people as contributors however it wants.

As a former or current (I really have zero clue at this point) Website WG member, I've seen @fhemberger working on this for years now and would +1 his suggestions on this in any case because he's been the one doing the work.

[ghost]

Not sure whether this auto bot starts or not, but now there're some contributors, and maybe they should be the Member of Nodejs.org before becoming the member of the specific language group, so if the auto bot isn't ready yet, would anyone can invite them into Nodejs.org?

@nodejs/nodejs-it：
@xela92 @aymen94

@nodejs/nodejs-ar：
@celyes

[MylesBorins]

@Maledong do you have reference to where they have made contributions or requested membership?

[fhemberger]

@Maledong Sorry, the idea with the bot has been postponed (see #282 (comment)), so I stopped adding new members at the moment.

Maybe we can add them as external collaborators to the language specific groups in the mean time. It doesn't give them commit rights to the website repo for now, but at least they can be @-mentioned when addressing the group.

[fhemberger]

For translations, I'd like to switch to Crowdin (as it is already used for the docs). I think the whole @nodejs/nodejs-* group thing could possibly be managed in a different way as well.

Ref: nodejs/i18n#72

[ghost]

@MylesBorins:
Here're the detail info of their contributions:

@celyes：nodejs/nodejs.org#2030
@aymen94：nodejs/nodejs.org#2024
@xela92：nodejs/nodejs.org#1762 (A huge pending submit).

[fhemberger]

I agree to add these three to the website group, also @Yash-Handa for his amazing work of going through all the old Nodejitsu knowledge base articles and updating them.

@MylesBorins Could you please add them?

(also I'm closing this issue, as we won't have an automated process for this.)

[MylesBorins]

I've added all 3 to the website group.

[fhemberger]

Thanks!

[Yash-Handa]

Thanks, @MylesBorins for adding us to the family ❤️

Btw, there were 4 of us, I think you forget me (@Yash-Handa) 😊