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
OmniAuth Community organization #836
Comments
I would also be available to help maintain with my spare cycles from helping with Bundler |
Sounds like a good idea. @sferik thoughts? |
As the progenitor of OmniAuth but someone who should no longer have any say On Thu, Aug 4, 2016 at 9:09 AM Olivier Lacan notifications@github.com
|
I’m all for it. What are the next steps to make this happen? |
Just let me know which people are the omniauth maintainers and I create a team and add you to the @omniauth group. |
@bufferoverflow I think that’s just: @mbleigh, @tmilewski, and me. |
Ok, I've invited you and made this team: https://github.com/orgs/omniauth/teams/omniauth-maintainers |
@bufferoverflow Hmmm, I just tried to update the homepage in the gemspec but it seems like I lost push access to the repo. Can you please double-check the permissions? |
@sferik I've given the I think it would also be good to make one or more members of the core OmniAuth team "Owners" of the |
@sferik I've gone ahead and made you an owner. |
👍 super cool! Thanks @md5 for helping out here! |
@sferik Excellent! Do you want to take care of adding the other OmniAuth committers to https://github.com/orgs/omniauth/teams/omniauth-maintainers? |
Wait, scratch that... I see that there are already pending invitations. |
It's so cool that we did this together! |
Just found that on the wiki, https://github.com/omniauth/omniauth/wiki Is this the official logo? |
I believe it is. It would be nice if someone from Intridea could provide the source file. Or I could try to redraw it as an SVG. On August 16, 2016 at 3:27:30 PM, Roger Meier (notifications@github.com(mailto:notifications@github.com)) wrote:
|
I've added the logo to the omniauth organization account. |
I think this can be closed. |
Agreed, closing now. |
As part of a recent discussion around the maintenance of the
omniauth-saml
provider gem (omniauth/omniauth-saml#67), a new @omniauth organization has been created.Currently, this organization only houses the
omniauth-saml
gem (moved fromPracticallyGreen/omniauth-saml
), but I wanted to get the thoughts of the OmniAuth maintainers and other members of the OmniAuth user community regarding this change.I could see it making sense to move some of the
omniauth-*
gems and perhapsomniauth
itself to this organization, particularly given the "Improved Organization Permissions" functionality that GitHub rolled out in the middle of last year (see this post: https://github.com/blog/2020-improved-organization-permissions). With these permissions, it would be relatively straightforward to have a team per provider or teams that span multiple related providers while still controlling ownership access more strictly.The last thing I would want to have happen is for anyone to get upset about this new organization, so that's why I'm raising the discussion here. I can't speak on behalf of other contributors to the new @omniauth organization, but I'm sure we all want to do what's best for the OmniAuth user community as a whole.
The text was updated successfully, but these errors were encountered: