On Saturday 09 August 2014 01:38:32 Curtis Maloney wrote: > For what it's worth, I can understand the opposition to requiring a GH > login [ostensibly a "coders" account] in order to make comments on tickets. > > However, if you're opinionated on a ticket you're either a coder, or feel > strongly enough to overcome such a [low] hurdle. > > Still, options of more than just GH would dissipate this issue...
As Aymeric noted (but it might have been "hidden" by the whole argument), Github is currently implemented; other options are welcome, but someone needs to add them. > those > without GH, BB and Twtitter accounts would be few, I'm sure, and tools like > python-oauth-toolkit give you many options easily. > I, personally, had Google and StackExchange in mind. I will probably add them, if all goes well and nobody opposes it, within two weeks (I am currently on a family vacation with busy days and a flaky connection). > Does this debate include removing the _existing_ auth? > Having both auth's together is problematic (perhaps it can be done, but again, somebody needs to do it). At the moment, you cannot login with a djangoproject.com user. Shai. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/201408090335.17664.shai%40platonix.com. For more options, visit https://groups.google.com/d/optout.
