-
Notifications
You must be signed in to change notification settings - Fork 188
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
Maintenance and forks #101
Comments
@Eric-Guo Please include anyone else who might be concerned. |
Good evening, I would like to propose that I will take over the project if m0n9oose-san don't mind. I maintain this repository: So then, please permit me to upload gem packages to Thank you! |
At the very least it would be great if the current Git snapshot could be published, as the current last version is missing OmniAuth 2 support. |
By the way, how about talking to people from @omniauth and moving the project under their namespace while simultaneously moving to group maintenance? |
just ping me as soon as you came to a common agreement, I created the omniauth org and can create a project there and add maintainers. @stanhu mabye also interesting for you |
@bufferoverflow Thanks for the ping! We've made significant improvements to this gem in https://gitlab.com/gitlab-org/gitlab-omniauth-openid-connect. I'd suggest starting with that. See https://gitlab.com/gitlab-org/gitlab-omniauth-openid-connect/-/blob/master/CHANGELOG.md for more details. |
What about the gem name? @m0n9oose What do you think? |
Cc @jjbohn, who I reckon still has upload rights for the original gem. |
hey guys. There are a lot of different proposals, which makes me a bit confused about what actually is going on. |
@m0n9oose, I guess I am to blame since I turned this discussion that way 😄 I guess the ultimate aim is to have One Good OpenID Connect strategy for OmniAuth. What do you think? |
@hhorikawa are you asking me to allow you to push your code from a completely different repository to rubygems.org using the same gem name as this repository? Sorry, but this sounds way too dangerous, considering there are a lot of projects that use this gem. If you have any proposals like improvements/fixes - you're welcome to open a PR. |
@andrewshadura sounds great to me. Do we have anybody from @omniauth here? Is it possible to move one of the forks under your namespace? |
I understand @bufferoverflow is. |
@andrewshadura ah, yeah, sorry I missed that. Great. @bufferoverflow can we just move existing repository under your namespace? |
I suggest the following:
WDYT? |
I made @m0n9oose an owner to start the transfer, also added https://github.com/orgs/omniauth/teams/omniauth-oidc with the maintainer crew ( @m0n9oose @hhorikawa @stanhu ). |
@bufferoverflow transfer is completed. omniauth-oidc team has been added as maintainer |
@stanhu @hhorikawa i need your email addresses to add you as owners to rubygems |
Welcome to the omniauth family! ❤️ I maintain the omniauth-identity gem. Please ping me if I can be of help! |
btw. I also made https://gitlab.com/omniauth long time ago so we can setup gitlab-ci if needed. omniauth/omniauth-org#3 |
Next idea: talk @jjbohn into uploading an empty gem |
I am so glad that my issue got this much traction! 🙂 |
@m0n9oose hidden. Thanks! |
Thank you! |
Done to update my README. |
@hhorikawa please enable 2FA on your rubygems account |
I have opened a few PRs during the past week, it feels bad to @mention to get any attention to it - or is that the way to go? |
@davidwessman be patient. Your efforts are appreciated, and PRs will be reviewed as soon as possible. Please keep in mind that we work on this in our free time when we have it. |
Thanks all! I would welcome help upstreaming my changes in https://gitlab.com/gitlab-org/gitlab-omniauth-openid-connect. In the interest of transparency, I've added a few colleagues with the We should probably have some lightweight process for giving merge access to those who actively help with this project. I welcome ideas here. |
@stanhu I think this makes sense as @alexkalderimis and @dblessing are working on the omniauth topics on your end. Maybe worth if they could start with first with some MRs here, so the other maintainers could build up trust. Maybe the gitlab-ci file you already had? I've setup the ci already here: https://gitlab.com/omniauth/omniauth_openid_connect btw. why this is important for me: https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/8018 and follow-up https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/2804 |
FYI, I filed a request with GitHub Support to disconnect this project form the original fork. That way pull requests will go directly to this project instead of the original project. I found it a bit confusing that new pull requests would default to the other project. 😄 |
@stanhu could you maybe add me as well to the omniauth_openid_connectoidc owners? My user name there: https://rubygems.org/profiles/bufferoverflow |
Hello!
Glad to see that there have been some updates for this gem.
When investigatint the pcke-feature (#80) I have found a few forks that seems to be active:
Would it make sense to merge ranks with anyone of them?
The text was updated successfully, but these errors were encountered: