--
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-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAKBiv3xybw0b26tamFS%2BMDuPPF8Ce5L7bqza6k08a2_u2eeMcg%40mail.gmail.com.
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.
--
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-develop...@googlegroups.com.
To post to this group, send email to django-d...@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/53B41C22-FAB6-49A9-9284-5BCCFC4D28BD%40polytechnique.org.
On 7 août 2014, at 02:58, Andre Terra <andre...@gmail.com> wrote:Did you just ask “how would Django as a project benefit from having
> Most importantly, how would Django as a project benefit from this
> choice other than reducing minimal spam?
core devs work on committing patches rather than fighting spam”?
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.
We already have that: https://www.djangoproject.com/~aaugustin/
> 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 limitedWe don’t have that.
> to GitHub.
Are you volunteering to do this work, and if so, when will it be done?
> TL;DR Identity on djangoproject.com, Authentication linked to multiple OAuth,
> Authorization in Trac.
I’m sorry, but ideas don’t matter nearly as much as execution here.
> I hope that idea makes sense. I may be just babbling nonsense.
We just need working tools — nothing fancy.
On Thu, Aug 7, 2014 at 3:46 AM, Aymeric Augustin <aymeric....@polytechnique.org> wrote:
On 7 août 2014, at 02:58, Andre Terra <andre...@gmail.com> wrote:Did you just ask “how would Django as a project benefit from having
> Most importantly, how would Django as a project benefit from this
> choice other than reducing minimal spam?
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?
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.
Many others before and after me have expressed a desire to
not have GitHub as a hard requirement.
Indeed, but I’m dismissing this argument because GitHub is thepragmatic choice, whether you like it or not. Also, this revealsthat your argumentation in favor of more planning was actuallyaimed at stalling the proposal.If you hate GitHub enough that you don’t want to use it, put yourtime where your mouth is and build a solution.But don’t ask me to keep deleting spam manually.
I’m sorry. Please accept my apologies and let me rephrase that withoutspam-fighting-induced frustration:“Other than reducing spam, Django as a project will benefit from thischange be freeing core dev time and energy currently used to deletespam manually and tweak a feeble anti-spam plugin. Core dev timeand energy are often cited as bottlenecks in the Django developmentprocess.”Other advantages have been put forward; I won’t rehash them.
Aymeric Augustin
<aymeric....@polytechnique.org>
writes:
You can, at present, participate in Django's bug tracker without a
> You're right. Then just remove "to submit pull requests" from my
> argument and it still holds, simply because the vast majority of the
> Django ecosystem is on GitHub, and you can't participate meaningfully
> without GitHub.
GitHub account.
The bug tracker contributions don't count, then? You consider
participation in bug tracker discussions to be meaningless?
--
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-develop...@googlegroups.com.
To post to this group, send email to django-d...@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/CANE-7mUMrhB1L7ej%3DN1hE70CFV_EiwBG16bV6FSVCUnU6ZOgkw%40mail.gmail.com.
Hi Aymeric,
Nice :)
--
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-develop...@googlegroups.com.
To post to this group, send email to django-d...@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/0dae599b-afcf-4a41-8c2b-75fead33754b%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CALE3ZjWgUyBYmN22__Qr0ikj-0M8wo2KjgmJzPVyrwYQJ6gpPQ%40mail.gmail.com.
--
Aymeric.
--
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-develop...@googlegroups.com.
To post to this group, send email to django-d...@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/5757E2E5-5496-4C59-A99E-87B5BC1AD276%40polytechnique.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq8494XsVQXQb-fda%2BA_CV0fXRGt916KZ-AseTRGYcO9LiJA%40mail.gmail.com.
Hi Russell,It seemed to me that this page wasn't nearly as good an introduction to contributing to Django as the contributing guide from the official docs, so I trimmed it and pointed to the docs instead.In fact, I started by removing incorrect or outdated information — for instance, the workflow described in the page dated back to the pre-git era, replacing get_absolute_url appeared to be the main current project while no one has worked on it for years, etc. A few minutes later there was so little left that I simply rewrote the page.Generally speaking, I don't believe we'll ever manage to keep the wiki sufficiently accurate and up to date to make it useful. Last year I tried to look for spam links (with a script) and scrub them, but there were so many that I gave up. In my opinion, the viable alternative to our self-hosted wiki is called the World Wide Web :-)Feel free to restore and perhaps update the previous content. I believe it did more harm than good, but as long as it remains clear that you need to authenticate before you can file a ticket, we'll be all right!
Is there a way to merge user accounts? Currently my github Account is c-schmitt, while my Trac user account ist merb.