Invite contributors to teams

[johno]

It'd be nice to add a "contributor" team to unified organizations which all contributors are invited to. There's precedent here with what Gatsby does and helps contributors receive a warm welcome to the community after getting a PR merged.

---

Rendered version

[wooorm]

Good idea! Thanks @johno, and also great feedback @ChristianMurphy!

I think this would be really good. When I kicked inactive people of the orgs, most people understood, but there was one person who was a bit annoyed and suggested something along these lines.

I feel the more active contributors (aka members) should receive precedence in tooling. We can do it manually at first, but of course we should try to automate it!
And contributors in general should be moved, when possible, to members (mergers, releasers), if they are so inclined (we could outline that process somewhere).

Finally, this RFC does affect the core collective governance document: https://github.com/unifiedjs/governance

[wooorm]

Some more follow up ideas / questions:

• I think this new team (contributors) can have the triage role: https://github.com/unifiedjs/governance/issues/18
• I think writers and releasers should be in members, respectively with the write and maintain roles
• How does this affect emeritus members? Should we drop emeritus and instead use contributors? I like that because that you don’t “phase people out” to inactive, but instead remove some of the rights / security risks they’re not using?

[johno]

I think this new team (contributors) can have the triage role: unifiedjs/governance#18

💯

How does this affect emeritus members? Should we drop emeritus and instead use contributors? I like that because that you don’t “phase people out” to inactive, but instead remove some of the rights / security risks they’re not using?

Yeah I'd guess that emeritus would become the contributor role. Same permissions apply.

[wooorm]

github-tools and npm-tools brings us very close to being able to do this automatically. We only need a humans.yaml in /governance and people will get invites daily.

I do foresee problems with a selection procedure:

• Who gets added? Someone that comments on a thread? Someone that fixes a typo? Someone that writes a PR without really understanding the problem?
• Who decides to add them? The member that comments first? The person that merges? Idea: should a member comment with something like: “Hey, thanks for this contribution, would you like to join us as a collaborator?” When the person agrees, the member whips up a PR to add their details?
• Do members get to vote / voice concerns?

Note: read/triage rights aren’t that dangerous.

Oh and last:

• Do we need to remove people that are not at all active? Every half year? Every year? What does it bring unified that we have 300 inactive collaborators with read rights?
• I’m interest on any insights about all of this from Gatsby folks!

[wooorm]

Final comment period! It’s almost ready to be implemented as the governance docs are updated for it.