RFE: Consolidate Repositories / Organizations

[agardnerIT]

Proposal

Keptn has an inordinate amount of repositories in three (!) different places (official): keptn, keptn-sandbox and keptn-contrib. Plus many other repositories from "key people" who fork and spin off their own demos.

I don't see the benefit to an ever growing and splintered set of repositories. On the other hand, I see lots of downside:

• Issues and PRs go stale
• Maintainers (of which we have too few) are overwhelmed with where and when to look - undoubtedly causing the problem above
• New (and existing) Keptn users (and potential contributors) have a difficult time finding information

Consolidating everything would bring us closer to a more streamlined, tidy and organised project.

No doubt there are limitations and reasons we have the setup we have, but I just don't think it needs to be that fragmented.

References

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".

[thschue]

I think it would be nice to drop the keptn-sandbox organization and stay with keptn and keptn-contrib, whereby keptn contains all top-level projects maintained by the keptn maintainers and keptn-contrib community-maintained extensions and add-ons.

[DavidPHirsch]

@mowies do we actually need the other orgs we have?

[mowies]

I think we should keep one of the other orgs for things like demo repos for talks and such things. I don't really care which one it is though.
This for example is one used by @grabnerandi : https://github.com/keptn-sandbox/klt-on-k3s-with-argocd
Or this one: https://github.com/keptn-sandbox/lifecycle-toolkit-examples

[DavidPHirsch]

@mowies @grabnerandi maybe we just move the two repos to this org? what do you think?

[mowies]

I think the initial thought was that the contrib or sandbox org is split off so that we can have repos there that are just maintained by single contributors without the full Keptn org having maintainer access and responsibility.
That's not really the case for the Keptn org. But of course we can change that. Although, in the Keptn org, permissions and settings are handle by config as code through peribolos, which would mean that "independent" repos would need to make change suggestions to the peribolos config to get things done