On Thu, Aug 7, 2014 at 3:46 AM, Aymeric Augustin < [email protected]> wrote:
> On 7 août 2014, at 02:58, Andre Terra <[email protected]> wrote: > > > Most importantly, how would Django as a project benefit from this > > choice other than reducing minimal spam? > > Did you just ask “how would Django as a project benefit from having > core devs work on committing patches rather than fighting spam”? > Did you just put on the worst attitude possible because someone asked an honest question? And, no, I asked what advantages are there for choosing GitHub other than the alternatives. As someone else aptly put it somewhere else in this thread, what if we decide we don't like GitHub anymore? If you don’t already have a djangoproject.com account, you’re likely to > give up on reporting a small bug just because it’s too complicated to > log in. Considering our target demographic, GitHub OAuth would > eliminate this problem. > > Also, if you’re trying to report a bug anonymously, you’re likely to be > unable to pass the CAPTCHA, and also be unable to report it, because > you’re still getting blocked by the CAPTCHA. See complaints: > https://code.djangoproject.com/search?q=captcha&noquickjump=1&ticket=on > > Finally, to be honest, I’d rather adjust Django’s tools to enthusiastic > beginners than grumpy freedom extremists who refuse to use GitHub. > > > A better solution would be to strengthen what it means to have an > identity > > on djangoproject.com. Rather than restricting user actions to Trac, we > > could motivate users to create something like a Django profile which > would > > be used for Trac (among may other uses) > > We already have that: https://www.djangoproject.com/~aaugustin/ Yes, I am well aware. Hence my use of the word "strengthen". > and could later be linked to any OAuth providers, including but not > limited > > to GitHub. > > We don’t have that. > > > TL;DR Identity on djangoproject.com, Authentication linked to multiple > OAuth, > > Authorization in Trac. > > Are you volunteering to do this work, and if so, when will it be done? > > > I hope that idea makes sense. I may be just babbling nonsense. > > > I’m sorry, but ideas don’t matter nearly as much as execution here. > We just need working tools — nothing fancy. I am sorry, I was under the impression that this was a mailing list. I wasn't aware we were on a coding sprint. I would say execution doesn't matter nearly as much as planning. I think it's common sense to establish a long term path before we taking the first step. Perhaps GitHub OAuth is a good solution for the spam problem, but on the other hand it may not be the ideal solution for Django as a community and project. Many others before and after me have expressed a desire to not have GitHub as a hard requirement. Are we more adamant about not adding code to contrib or using X or Y javascript framework than we are about adding GitHub as a requirement to the project? The ad hominem attacks and harsh attitude definitely do not make an inviting atmosphere for new and old contributors alike. Consider rethinking that. -- AT -- 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/CAKBiv3yJejuTe%2B%2Bz3JHFNqzv3c3x-Am-WViND9hEM5W_BZnX%2BQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
