Skip to content
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

Closed
md5 opened this issue Feb 10, 2016 · 21 comments
Closed

OmniAuth Community organization #836

md5 opened this issue Feb 10, 2016 · 21 comments

Comments

@md5
Copy link
Contributor

md5 commented Feb 10, 2016

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 from PracticallyGreen/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 perhaps omniauth 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.

@coilysiren
Copy link

I would also be available to help maintain with my spare cycles from helping with Bundler

@olivierlacan
Copy link

Sounds like a good idea. @sferik thoughts?

@mbleigh
Copy link
Contributor

mbleigh commented Aug 4, 2016

As the progenitor of OmniAuth but someone who should no longer have any say
in its development, I'm in favor :)

On Thu, Aug 4, 2016 at 9:09 AM Olivier Lacan notifications@github.com
wrote:

Sounds like a good idea. @sferik https://github.com/sferik thoughts?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#836 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAD_prMUTs88qw_S_HlW96MuEPa9eJXks5qcg7NgaJpZM4HXGuf
.

@sferik
Copy link
Contributor

sferik commented Aug 4, 2016

I’m all for it. What are the next steps to make this happen?

@bufferoverflow
Copy link
Member

Just let me know which people are the omniauth maintainers and I create a team and add you to the @omniauth group.

@sferik
Copy link
Contributor

sferik commented Aug 5, 2016

@bufferoverflow I think that’s just: @mbleigh, @tmilewski, and me.

@bufferoverflow
Copy link
Member

Ok, I've invited you and made this team: https://github.com/orgs/omniauth/teams/omniauth-maintainers
Now you should be able to move the repo.

@sferik
Copy link
Contributor

sferik commented Aug 5, 2016

@sferik
Copy link
Contributor

sferik commented Aug 5, 2016

@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?

@md5
Copy link
Contributor Author

md5 commented Aug 5, 2016

@sferik I've given the omniauth-maintainers team "Admin" access to the omniauth repository.

I think it would also be good to make one or more members of the core OmniAuth team "Owners" of the omniauth organization.

@md5
Copy link
Contributor Author

md5 commented Aug 5, 2016

@sferik I've gone ahead and made you an owner.

@sferik
Copy link
Contributor

sferik commented Aug 5, 2016

@md5 👍 I just successfully pushed to the repo: b9bc3bb.

@bufferoverflow
Copy link
Member

👍 super cool! Thanks @md5 for helping out here!

@md5
Copy link
Contributor Author

md5 commented Aug 5, 2016

@sferik Excellent! Do you want to take care of adding the other OmniAuth committers to https://github.com/orgs/omniauth/teams/omniauth-maintainers?

@md5
Copy link
Contributor Author

md5 commented Aug 5, 2016

Wait, scratch that... I see that there are already pending invitations.

@bufferoverflow
Copy link
Member

It's so cool that we did this together!
Do we have an OmniAuth logo that we can add to our omniauth organization account?

@bufferoverflow
Copy link
Member

Just found that on the wiki, https://github.com/omniauth/omniauth/wiki

logo

Is this the official logo?

@olivierlacan
Copy link

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:

Just found that on the wiki, https://github.com/omniauth/omniauth/wiki

Is this the official logo?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub(#836 (comment)), or mute the thread(https://github.com/notifications/unsubscribe-auth/AAEBnr0WSfDHQKadntlQaeShGY9FY6thks5qgg8igaJpZM4HXGuf).

@bufferoverflow
Copy link
Member

I've added the logo to the omniauth organization account.

@md5
Copy link
Contributor Author

md5 commented Apr 28, 2017

I think this can be closed.

@tmilewski
Copy link
Member

Agreed, closing now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants