Consider creating GH orgs for each working group

[chipchilders]

Based on my comment in #31 :

We may struggle to keep this up to date... I know Chris Clark struggles to keep it up to date for the analytics dashboards. One option, which we don't need to solve for right now, might be to start moving repos into GitHub organizations dedicated to each working group. We could keep a shared GitHub org for the community repo, private repos (for CI config) and other shared code / resources.

[julz]

Another option is to use a bot to manage the repos and permissions based on a yaml in a repo. Knative uses peribolos for this, for example, e.g. https://github.com/knative/community/blob/master/peribolos/knative.yaml.

[chipchilders]

Another option is to use a bot to manage the repos and permissions based on a yaml in a repo. Knative uses peribolos for this, for example, e.g. https://github.com/knative/community/blob/master/peribolos/knative.yaml.

Good info. Thanks @julz !

[loewenstein]

I don't think spreading CF code over more orgs than already (I consider cloudfoundry-incubator a distraction when looking for repos) would be a good move. Automation sounds like the right thing to keep things in sync.