And if for some reason you can't login since it was removed (and you had no
other associated accounts), just send the details to supp...@ansible.com
and we can get things sorted out.

James Cammarata
Director, Ansible Core Engineering
github: jimi-c

On Thu, Aug 27, 2015 at 2:39 PM, Greg DeKoenigsberg <g...@ansible.com>
wrote:

> On Thu, Aug 27, 2015 at 2:26 PM, Hristo Stoyanov <hr.stoya...@gmail.com>
> wrote:
> > I think the idea to link up Galaxy account to Github as the only auth
> > service is wrong. This is why neither Github not Docker hub do it.
>
> Certainly willing to discuss it. :)
>
> > Here is why:
> > I created an account in Github, used that account to log into Galaxy and
> add
> > my roles. Then deleted my account in GitHub (but still use the
> repositories
> > there and organization under different github account).
>
> OK, I'm confused. From Github:
>
> "Deleting your user account removes all repositories, forks of private
> repositories, wikis, issues, pull requests, and pages."
>
> So if you delete your account, how are you still using your
> repositories?  I'm guessing that you forked them elsewhere, and are
> now working with forks of a since-deleted project. Which is how it
> should work in Galaxy as well, right?
>
> > Now i can no longer log into my old Galaxy account and the roles I added
> are unmanageable and basically junk.
>
> If you really delete the Github account, the roles you added from that
> account would have been broken anyway because Galaxy pulls them from
> the originally associated Github repo, which would no longer be there.
> This is precisely the kind of scenario we're trying to detect and
> mitigate.
>
> > Another problem is that I am forced to use the same username
> > as my Github username, if I choose to open a new Galaxy account.
>
> Is there a reason you object to that?
>
> > Any ideas how can I recover my Galaxy account?
>
> You should still be able to login to your old Galaxy account and use
> it until the switchover happens.  We're waiting until January to (a)
> make sure it's the right thing (I think it still is) and (b) give
> plenty of time to identify and work out corner cases.
>
> --g
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Ansible Project" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to ansible-project+unsubscr...@googlegroups.com.
> > To post to this group, send email to ansible-project@googlegroups.com.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/ansible-project/09c5249c-bb75-4342-b096-4062fb0b3738%40googlegroups.com
> .
> > For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> Greg DeKoenigsberg
> Ansible Community Guy
>
> Find out why SD Times named Ansible
> their #1 Company to Watch in 2015:
> http://sdtimes.com/companies-watch-2015/
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/CAM1FbhH9L6PyEWfdm0S72XPu1NDGkzmJbBHHR3bNSWF5t85aGQ%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFjOxZm0Y8fGRXimfsRg3xRv4ki-dxNXkdjWTmB-039Ttg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to