[bisq-network/bisq] Update Bisq Github teams to include active members and remove inactive members (#5422)

[Chris Beams]

> Not sure if this falls under the role of @bisq-network/team-leads or @bisq-github-admin-3 / @ripcurlx

This would fall under the @bisq-network/roles-maintainers, for which I am the role owner.

The team structure is probably overkill at this point. The reasons they exist are:

1. To reflect and codify role assignments defined in the issues in the bisq-network/roles repository
2. To allow for @mentioning and getting the attention of role owners without having to look up their specific usernames
3. To assign role owners appropriate access to repositories
4. To be used for focused team communication via GitHub Team Discussions

Reason (1) is not strictly necessary. We record role assignments in the role issues already, so having it reflected in GH team structures is actually duplication.

Reason (2) is handy, but it doesn't get used a whole lot.

Reason (3) is useful too, but only for a subset of teams/roles, certainly not all 62.

Reason (4) is obsolete. Using GH Team Discussions never really worked out, despite trying pretty hard to make it happen.

My suggested course of action would be to go through the teams with the intention of removing many or even most of them that do not directly benefit from (2) and especially (3). Leave the ones in place that are practical, and make sure they reflect the current assignments.

Further feedback welcome. Thanks for raising the issue @pazza83.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/5422#issuecomment-828292128
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210428/f93f385c/attachment.htm>