In that case, is it easy enough to support github oauth + the current trac auth concurrently? If a user chooses to go through the harder path, that's fine.
I like the idea of using github oauth. Password managers usually have a miserable time supporting HTTP basic auth. On Thursday, 7 August 2014 10:44:08 UTC+10, Ben Finney wrote: > > Aymeric Augustin > <[email protected] <javascript:>> > writes: > > > In order to fix the spam problem while maintaining an easy workflow, > > I'm proposing to require GitHub auth for all "write" operations: > > creating a ticket, adding a comment, etc. Most people interested in > > Trac should have a GitHub account already. > > −1. I am happy to agree to Django's BTS terms of use, not GitHub's. > Please don't make the former depend on the latter. > > -- > \ “Isn't it enough to see that a garden is beautiful without | > `\ having to believe that there are fairies at the bottom of it | > _o__) too?” —Douglas Adams | > Ben Finney > > -- 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/c56a5824-da8a-4b2a-9682-0f4a49aaa1f3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
