On Wed, Aug 6, 2014 at 9:47 PM, Shai Berger <s...@platonix.com> wrote:

> Today, it is possible to contribute to the Django project without a
> Github account. I would like this to remain the case.
>

This is the most important argument for the -0. In fact, as a seldom code
contributor but long time user and commenter on trac tickets, if I had to
vote, I would actually -1 on the basis of not wanting to give that blessing
to GitHub on an exclusive basis. If were are considering other OAuth
providers, "now is better than ever" lest GitHub take over as a de facto
standard that may never be overcome.

Most importantly, how would Django as a project benefit from this choice
other than reducing minimal spam?

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) and could later be linked to any
OAuth providers, including but not limited to GitHub.

TL;DR Identity on djangoproject.com, Authentication linked to multiple
OAuth, Authorization in Trac.

I hope that idea makes sense. I may be just babbling nonsense.


Cheers,
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/CAKBiv3xybw0b26tamFS%2BMDuPPF8Ce5L7bqza6k08a2_u2eeMcg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to