Sorting org members

[JimMadge]

I've been taking a look through the organisation teams and members.

I think we should aim to have access/roles come from teams, and not assign to individuals. The latter quickly get difficult to manage and can lead to lingering permissions.

There are a few outside collaborators, who seem inactive now. Not wanting to give the impression they are not welcome by just revoking collaborator status, I'm inviting each to the org as a member of the Alumni team. That team has read access, but not write/maintain.

I hope that is a good signal that they are valued and welcome whether or not they are active maintainers/contributors. What do you think @all-contributors/maintainers ?

[flpm]

+1 teams makes it much easier to manage changes in the future by associating permissions to specific "roles" rather than individuals

[da5nsy]

Sounds like a good idea to me

[lwasser]

yes + 💯 to teams - so much easer to manage. @JimMadge what do you think about also having permission teams mostly for documentation. So for instance we've had to hunt down who has access to what here. what if just created a

npm team
release manager team
etc.

that way for our future selves, who can control what is in one place in this org.

[lwasser]

I just was thinking this because we have 3 repos we are maintaining here. Right now docs are spread across all of them and permissions to various accounts are also spread around the org (and outside the org).

[Berkmann18]

I agree.