Hi Wojciech, I believe we have it described into our README files
, but if
there's something that should be improved, please let us know.
GitHub issues are disabled for all the repositories because it's
really hard to watch issues on GH and keep up with Jiras.
At the moment we don't have enough bandwidth for it and there's no way
to sync between both.
On Thu, Nov 28, 2019 at 9:12 AM Wojciech Trocki <wtrocki(a)redhat.com> wrote:
---------- Forwarded message ---------
From: Wojciech Trocki <wtrocki(a)gmail.com>
Date: Thu, 28 Nov 2019, 11:57
Subject: Disabled issues section on keycloak github page.
To: keycloak-dev <keycloak-dev(a)lists.jboss.org>
I have been at the conference recently and chatted with a couple of
developers about keycloak.
What really made me worried that one of the devs made claim that:
"Keycloak does not allow the community to log issues"
Upon later explanation, I have found out that this was
misunderstanding related to the disabled issues section on the keycloak
Is there any reason why GitHub issues are disabled for keycloak?
I know that the team is using Jira for issue tracking.
GitHub issues became an open-source standard over the couple of years.
keycloak-dev mailing list