Support managing GitHub organization via CLOWarden

[austinlparker]

Hi! I'm a maintainer of OpenTelemetry, and we're interested in adopting CLOWarden to manage repos, teams, and organization users. I initially thought CLOWarden would be a 'drop-in' solution for us, but it appears that it is not, mostly due to one reason -- CLOWarden expects that organization membership is tied to team membership. In OpenTelemetry, we do not necessarily follow this -- contributors become org members first, then are added to specific teams as they move up the contributor ladder.

After looking at the way that other projects which use CLOWarden manage their GitHub orgs, I can see the logic in how CLOWarden does it (adding people as external collaborators to a repo, for instance) -- but I am curious, if we decide to maintain our current strategy for managing membership, would y'all be willing to accept a PR that added a new, 'merged' configuration file format that combined the CNCF and Sheriff concepts that we could use to hoist org membership into CLOWarden with? In essence, I'm thinking of something like this for a format --

organizaton: foo
members:
  - name: bar
    github: FooBar
    slack: "@foobar"
    website: https://foobar.io
  - name: baz
    github: BazQuuz
    slack: "@bigbaz"
    website: https://bazbutnotbazel.com
repositories:
  - name: my-cool-repo
    teams:
      - team1
    settings:
      has_wiki: true
      is_featured: true
teams:
  - name: team1
    maintainers:
      - bar
    members:
      - baz
// etc, etc.

[tegioz]

Hi @austinlparker 👋

Thanks for your interest in CLOWarden!

We'd like to keep this tool as simple as possible for now, and adding support to manage organizations' members isn't in our roadmap at the moment. But we'll keep you posted if the situation changes 🙂

P.S.: as a curiosity, I wanted to share that CLOWarden is able to read users data from the CNCF's people.json file as well. This is the source we use to feed users into the directory. However, even though users changes are made available to the service handlers, the only one available at the moment (GitHub) doesn't react to any of them (i.e. no action is taken in GitHub when a new user is added). Like I mentioned, our goal is to keep everything as simple as possible. But if you consider creating your own fork at some point, maybe this information could be helpful 😇

[austinlparker]

Yes, I noticed that when I was poking around. Thanks for responding!