Re: Requiring GitHub login for actions on Trac

2014-08-26 9:48 GMT+02:00 Christian Schmitt : > Is there a way to merge user accounts? Currently my github Account is > c-schmitt, while my Trac user account ist merb. > Technically, there's no such thing as a Trac account, just a username attached to tickets and

Re: Requiring GitHub login for actions on Trac

Is there a way to merge user accounts? Currently my github Account is c-schmitt, while my Trac user account ist merb. — Best Regards Christian Schmitt c.schm...@briefdomain.de Am 24.08.2014 um 21:52 schrieb Ben Finney : > Aymeric Augustin >

Re: Requiring GitHub login for actions on Trac

Aymeric Augustin writes: > Contributors who refuse GitHub's ToS can participate on Trac again. For working to fix this, and for acknowledging these people are contributors: Thank you! -- \ “Truth is stranger than fiction, but it is because fiction is

Re: Requiring GitHub login for actions on Trac

On Sunday 24 August 2014 20:44:30 Aymeric Augustin wrote: > > Eventually, I managed to set up DjangoProject and GitHub auth in parallel. > > Contributors who refuse GitHub's ToS can participate on Trac again. > > Issues created by username mismatches have been dealt with. Thanks, Aymeric, for

Re: Requiring GitHub login for actions on Trac

On 9 août 2014, at 21:21, Aymeric Augustin wrote: > I tried to support both Trac auth and GitHub auth but I couldn't make it work. Eventually, I managed to set up DjangoProject and GitHub auth in parallel. Contributors who refuse GitHub's ToS can

Re: Requiring GitHub login for actions on Trac

I've just updated the wiki homepage, restoring a few pieces of content from the older page. I agree most of the old content wasn't relevant any more, so the changes are mostly about the tone of the page. Hopefully the content in the new version is a little more inviting to newcomers. I'm sure

Re: Requiring GitHub login for actions on Trac

I think that much better option would be to link "Code" in header of djangoproject.com to this: https://docs.djangoproject.com/en/1.6/internals/contributing/ and make this a landing page for people who want to contribute. As a newbie contributor I found it super helpful :) On Friday, August

Re: Requiring GitHub login for actions on Trac

On Thu, Aug 14, 2014 at 7:20 PM, Aymeric Augustin < aymeric.augustin.2...@polytechnique.org> wrote: > 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

Re: Requiring GitHub login for actions on Trac

I just discovered this change (require Github for login) today and had a hard time finding this discussion. Maybe a link in the wiki would help? While I agree with the decision to move on to Github Login (finally no more basic auth!) I'd like to have a way to merge my two accounts. Especially

Re: Requiring GitHub login for actions on Trac

I was looking at the wiki page myself a few weeks ago an noticed it was horribly out of date. I might be nice to keep that page minimal (maybe just a few links to other pages) because normal users aren't allowed to edit it. -- You received this message because you are subscribed to the Google

Re: Requiring GitHub login for actions on Trac

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

Re: Requiring GitHub login for actions on Trac

Hi Aymeric, I just noticed that the content on the wiki homepage has been massively altered, replaced with a "please login with GitHub" text. Was this change deliberate? The wiki landing page is linked from the homepage as code.djangoproject.com, and has always held a collection of useful

Re: Requiring GitHub login for actions on Trac

On Sunday, August 10, 2014 2:37:01 AM UTC-7, Aymeric Augustin wrote: Using GitHub for auth a giant +1 from me. For me, this ranks up with the SVN to Github move as a: "Why hasn't this been done already?" Daniel Greenfeld co-author Two Scoops of Django -- You received this message because

Re: Requiring GitHub login for actions on Trac

Am 09.08.2014 21:21, schrieb Aymeric Augustin: I tried to support both Trac auth and GitHub auth but I couldn't make it work. The argument that "I use GitHub but maybe someone else doesn't want to" came up a few times in this discussion. It seems to me that it's a theoretical concern about an

Re: Requiring GitHub login for actions on Trac

Don't worry, I remapped permissions to GitHub usernames. Curtis, I lowercased your username, you should still have admin rights. There were a few usernames I had never seen and couldn't identify. If you think you lost permissions, please get in touch privately. As said earlier by Florian, it's

Re: Requiring GitHub login for actions on Trac

I ran into that exact problem when djangopackages changed... case mis-match meant it took months before I had access again. On 10 August 2014 09:35, Luke Granger-Brown wrote: > My only concern with this is the thing with the usernames, whereby some > people don't use the

Re: Requiring GitHub login for actions on Trac

My only concern with this is the thing with the usernames, whereby some people don't use the same username on Trac as on GitHub, and that accounts are automatically munged together if they have the same username. As a demonstration, I found someone with the core developer tag on Trac (lukeplant)

Re: Requiring GitHub login for actions on Trac

Nice :) On Saturday, 9 August 2014 21:22:07 UTC+2, Aymeric Augustin wrote: > > Uhmm... but I see you moved forward and already did it? > > Yes, I did. > > -- > Aymeric. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To

Re: Requiring GitHub login for actions on Trac

Hi Wim, Thanks your your feedback. On 9 août 2014, at 12:00, Wim Feijen wrote: > I am in favour of *adding* github as an authentication tool. We would benefit > immensily for making it easier for new people to log in and contribute. Would > it be possible to add that to

Re: Requiring GitHub login for actions on Trac

> > Hi Aymeric, Thanks for your proposal and your work on this! I am in favour of *adding* github as an authentication tool. We would benefit immensily for making it easier for new people to log in and contribute. Would it be possible to add that to Trac, so people who have moral

Re: Requiring GitHub login for actions on Trac

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

Re: Requiring GitHub login for actions on Trac

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

Re: Requiring GitHub login for actions on Trac

2014-08-08 8:55 GMT+02:00 Ben Finney : > Aymeric Augustin > > writes: > > > 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

Re: Requiring GitHub login for actions on Trac

On Fri, 2014-08-08 at 08:39 +0200, Aymeric Augustin wrote: > 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. > >

Re: Requiring GitHub login for actions on Trac

Aymeric Augustin writes: > 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. You

Re: Requiring GitHub login for actions on Trac

2014-08-08 7:19 GMT+02:00 Shai Berger : > On Friday 08 August 2014 01:49:55 Ben Finney wrote: > > Aymeric Augustin writes: > > > GitHub doesn't require creating a new account, since anyone interested > > > in contributing to Django should

Re: Requiring GitHub login for actions on Trac

On Friday 08 August 2014 01:49:55 Ben Finney wrote: > Aymeric Augustin writes: > > GitHub doesn't require creating a new account, since anyone interested > > in contributing to Django should have a GitHub account already to > > submit pull requests. > > This

Re: Requiring GitHub login for actions on Trac

Aymeric Augustin writes: > GitHub doesn't require creating a new account, since anyone interested > in contributing to Django should have a GitHub account already to > submit pull requests. This seems to be a common assumption, but it's not true — unless you

Re: Requiring GitHub login for actions on Trac

> I'm sorry. Please accept my apologies and let me rephrase that without > spam-fighting-induced frustration: > > "Other than reducing spam, Django as a project will benefit from this > change be freeing core dev time and energy currently used to delete > spam manually and tweak a feeble

Re: Requiring GitHub login for actions on Trac

Hi, Aymeric, Thank you for your e-mail. I sympathize with your frustration. On Thu, Aug 7, 2014 at 3:27 PM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > Indeed, but I’m dismissing this argument because GitHub is the > pragmatic choice, whether you like it or not. Also, this

Re: Requiring GitHub login for actions on Trac

Hi Andre, On 7 août 2014, at 19:57, Andre Terra wrote: > On Thu, Aug 7, 2014 at 3:46 AM, Aymeric Augustin > wrote: > On 7 août 2014, at 02:58, Andre Terra wrote: > > > Most importantly, how would Django as a

Re: Requiring GitHub login for actions on Trac

On Thu, Aug 7, 2014 at 3:46 AM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > On 7 août 2014, at 02:58, Andre Terra wrote: > > > Most importantly, how would Django as a project benefit from this > > choice other than reducing minimal spam? > > Did you just

Re: Requiring GitHub login for actions on Trac

+1 on GitHub OAuth. I've avoided filling or commenting on bugs because setting up Yet Another Account was enough friction that I never did it. On Thursday, August 7, 2014 2:21:06 AM UTC-5, Erik Romijn wrote: > > > Using GitHub makes sense as it's very likely a new contributor already > has a

Re: Requiring GitHub login for actions on Trac

On Thu, Aug 7, 2014, Schmitt, Christian wrote: >Currently we already live in a world were everything gets connected. And >that is really awful. One must consider that Github is definitely a target >for intelligence agencies. And I don't mean the NSA only. >Maybe I'm a

Re: Requiring GitHub login for actions on Trac

Absolutely +1. Clearly the most pragmatic choice. On Thursday, 7 August 2014 13:43:45 UTC+1, Josh Smeaton wrote: > > I don't think "vendor lock in" is a good enough reason to avoid it. If > GitHub were to go away, the move to a new code platform would be the > greater problem. Also, nothing

Re: Requiring GitHub login for actions on Trac

I don't think "vendor lock in" is a good enough reason to avoid it. If GitHub were to go away, the move to a new code platform would be the greater problem. Also, nothing will be "lost". The old usernames will still be there, they just won't be properly linked to your github username. I don't

Re: Requiring GitHub login for actions on Trac

Thank you for working on this, Aymeric. I am definitely +1 on moving to GitHub as sole authentication provider for trac. We could argue about this forever. In the mean time the spam will pile up, core developers will have to spend time deleting all of it, and eventually we'd come to a plan which

Re: Requiring GitHub login for actions on Trac

I'm a little bit concerned about that. First I'm using a different user on Trac than on Github, so everything I wrote so far will getting lost (not that bad problem for me), but I think there are many users who are in the same situation. The next thing is vendor lock-in. What will happen if

Re: Requiring GitHub login for actions on Trac

To be clear, I have a working implementation of GitHub OAuth that I can activate as soon as we reach a consensus. On 7 août 2014, at 02:43, Ben Finney wrote: > −1. I am happy to agree to Django's BTS terms of use, not GitHub's. > Please don't make the former depend

Re: Requiring GitHub login for actions on Trac

On Wed, Aug 6, 2014 at 8:59 PM, Josh Smeaton wrote: > 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

Re: Requiring GitHub login for actions on Trac

Alex Gaynor writes: > For new users, being able to reuse existing authentication credentials > is a considerable step up Agreed. This is an argument to allow OAuth login. It is not an argument to privilege any OAuth provider over others, or any OAuth provider over no

Re: Requiring GitHub login for actions on Trac

+1 for Github. Here's why: You're all focused on existing users. For new users, being able to reuse existing authentication credentials is a considerable step up, I regularly give up on filing bug reports against other OSS projects because I'm frankly too tired to register for

Re: Requiring GitHub login for actions on Trac

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

Re: Requiring GitHub login for actions on Trac

On Wed, Aug 6, 2014 at 9:47 PM, Shai Berger 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

Re: Requiring GitHub login for actions on Trac

Hi, > On 08/06/2014 03:30 PM, Tim Graham wrote: > > I proposed the idea a couple months ago and got several +1's. The main > > concern was from Shai, "not quite -1, but a strong -0 on "blessing" any > > single oAuth provider. GitHub is fine, but so are Google, StackExchange, > > and even the Evil

Re: Requiring GitHub login for actions on Trac

Aymeric Augustin 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

Re: Requiring GitHub login for actions on Trac

+1 from me. I don't see a problem with supporting only GitHub OAuth in this case. Django is hosted on GitHub, and any code contribution (which is ultimately what Trac is all about) will happen via GitHub, so it seems quite natural to me to support GitHub OAuth rather than any other arbitrary

Re: Requiring GitHub login for actions on Trac

I proposed the idea a couple months ago and got several +1's. The main concern was from Shai, "not quite -1, but a strong -0 on "blessing" any single oAuth provider. GitHub is fine, but so are Google, StackExchange, and even the Evil Empires(TM)."

Requiring GitHub login for actions on Trac

Hello, If you're subscribed to django-updates, you may have noticed that some spam is getting through since a few days. This is a negligible percentage of the amount of spam our defenses are fending off (about 4000 / day) but it's annoying. We're allowing anonymous bug reports because the