RFE: Onboard Keptn-sandbox and keptn-contrib to peribolos

[aepfli]

Proposal

We have an excellent repository and user management in place, so we should use it as much as possible to increase transparency.
The following logic step is to onboard the next GitHub Organizations.

• keptn-sandbox
• keptn-contrib

These organizations have few members and only a few people work within them.
Currently, a lot of those members are maintainers within those organizations.
Hence, keep the configuration minimal and add everyone (except certain privileged users) to the global maintainers or invite users only directly to the repositories.
The effort of defining and maintaining workgroups is too high compared to the reward.
The critical feature is the control of the repositories and coordinating creation via peribolos.

References

#225 is also related to this - and if we tackle both, we should most likely do them together

Sponsors

• (at)sponsor-1
• (at)sponsor-2

Checklist

• The idea is brought up for a discussion in a relevant Keptn Slack channel (use #keptn-project by default)
• Each sponsor should reply to this issue with the comment "I support".

[bradmccoydev]

I support this.

[agardnerIT]

I support this too if it simplifies things!

[DavidPHirsch]

are there actually any repos still in use? @bradmccoydev @agardnerIT