Add GitHub policy

[wooorm]

Rendered version

Hey folks! 👋

This document describes the GitHub policy I’m implementing for the orgs now.
This document is based on GH-2 and also based on some research and automation tooling I built in remarkjs/governance (which is the wrong place for it :p)

The tooling is pretty interesting. It automated so much of this stuff. It’s based on our team structure, the team members, and a list of outside collaborators. Finally, from that it creates a GitHub team structure from another config file.
It adds people when needed, and warns when people have rights they shouldn’t have.

Other than the stuff described in GH-2 and implementing mergers/releasers here, I’ve also added a section describing the creation/moving/archiving/removing of repos, and the removing/blocking of team members/individuals.

Again, up for review! (and I took inspiration from Node)

/cc @unifiedjs/core @unifiedjs/moderators

[zcei]

What is the process for moving a team member to emeritus state? Is this done only on request of the affected maintainer, after a given time period of no contributions (code, issue/PR replies, forum activity) or should the removal process be followed but in the organization's governance repo?

[wooorm]

@zcei In #2, the core team has a responsibility to review team members:

Review inactive team members. The core team periodically reviews the list of team members to identify inactive team members. Past members are typically given Emeritus status. Emeriti may request that the their status is restored.

I think the process of such a role change isn’t just about GitHub, but affects the main governance draft and other policies as well, so maybe it can go in the on and offboarding policy (currently proposed in #6).