Repository navigation
Replies: 1 comment 2 replies
|
We have had very few requests for RPMs, maybe 5-10 people asking for it in the many years we've been doing Keycloak. As such we simply can't prioritise it. In terms of community maintained RPMs that's a nice idea, but question is how do you trust such community maintained RPMs? I'm sure you have the best intentions here, but at the same time those RPMs could be compromised at some point. For this reason we simply can't support the maintenance of these, because at the same time we would be officially blessing the RPMs and sending a message to the wider community that we trust them, while at the same time we have no way of actually validating that. |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I will copy the issue #17066 because it was closed without proper discussion.
@stianst can you elaborate on why RPMs are out of scope, and if the team can support the maintenance of the package by adding a simple webhook to copr?
All reactions