-
Notifications
You must be signed in to change notification settings - Fork 399
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
the project active? #203
Comments
Is there an active fork? |
I've one in progress, still early stage due to low priority |
Hey, we forked this repo some time ago with the intention to only accept security fixes. However, I can see that with how Golang develops, there are some more fixes and repo maintanence that seems to be necessary in order to keep the project usable. Is unfortunate that ever since our fork, a bunch of the people who would help maintaining the repo left, so right now it's just me and there's a lot of other work to do, too. I am aware of the current sorry state of it. I'll try to dedicate some time to straighten it out a little bit in the future weeks. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/lifecycle frozen |
Is this project used anywhere within Red Hat, @stlaz ? If not, I wonder how you feel about recommending users to migrate to Keycloak, since it sees active development and is in the Red Hat portfolio as RH-SSO. As for your awesome-go list, @avelino , how about replacing it with Zitadel, which is also an OAuth2 server written in Go? |
last commit was made day
Oct 25, 2019
, more than 1 year ago, the project is listed in awesome-go and we have software checking inactive projects to remove from the list if it is not activeref: avelino/awesome-go#3316
The text was updated successfully, but these errors were encountered: