Hello! So… Since I’ve begun my migration towards deSEC, I’ve found that I had to push for tiny improvements in a lot of webhooks and providers that are maintained by the open community. The awesome people behind don’t necessarily have time to review my changes.
While I can operate with my fixed forks, I’d prefer that there is only ever one, say, terraform/opentofu provider, one external-dns webhook, one cert-manager webhook, one terranix module, etc., and that they’re all “above capacity” in terms of addressing small changes. But since that is not the case, I stand to maintain a lot of forks with inappropriately identical names.
Since I come from the Nix community, I am wondering if deSEC would be interested in a similar model as the GitHub “nix-community” org: It maintains a lot of unofficial projects that are widely used, but where the governance is more scattered. All projects are maintained by active community members, but without direct oversight from the parent organisation.
That is, what would deSEC think of a GitHub org called “desec-community” with maintained forks of the most popular providers, webhooks, REST clients and whatnot, as they get orphaned?