Dear Georges, On Sat, Aug 18, 2012 at 01:02:53PM +0200, Boris FELD wrote: > >> I'm sorry but I've already spent more time and effort than 99% of > >> casual contributors are expected to spend in 2012, namely: > >> > >> - Looked for a "submit new ticket" link or button on the tracker page, > >> didn't find one, figured it doesn't allow anonymous tickets.
True, it does not. The goal is to prevent spam, but the downside is that it makes things more difficult for occasional contributors. > >> - Signed up for yet another site account I'll probably won't have to > >> visit again. Since you created an account (https://www.logilab.org/cwuser/gsakkis) on logilab.org, you should now be able to add tickets to projects. > >> - Emailed to python-proje...@logilab.org 10 days ago, got an > >> auto-reply that my email is being held until the list moderator can > >> review it for approval, reason being "Post by non-member to a > >> members-only list". WTF was the signup for if I am still not a > >> member? True, there is no synchronization of accounts between the mailing lists and the website. > >> - Somehow found the Mailman page and registered for yet another > >> useless (to me) mailing list, powered by ugly antiquated > >> software. Mailman 2.1.11 is the one that's included in Debian stable. I guess you can call it "old" since it was released on June 2008, but it is kind of a standard, isn't it ? > >> - Posted the email that actually appeared on the list, including a > >> clean patch with updated passing tests. Thank you. > >> - Was asked to jump through one more hoop to create a ticket on the > >> tracker for whatever policy/bookkeeping reasons. The code review process of pylint mandates to link patches to tickets. It is true it makes things more complex for the occasional contributor. > >> - I tried to login to logilab.org for creating the ticket and was > >> welcomed by an an invalid SSL certificate. It is valid until nov 11th 2012, but it is true we did not pay a well-known certificate authority to sign it and you probably got an extra click in your browser to accept it and get thru. > >> - After adding a temporary certificate exception, There. > >> I got authentication > >> failure. Not very likely given that I use LastPass for auto generating > >> and entering passwords. > >> - Oh what the hell, let's pretend I forgot my password and enter my > >> email and captcha for recovery. > >> - Password recovery email arrives but it's broken too: > >> """ > >> If you requested this password change, please set a new password by > >> following the link below: > >> > >> None > >> """ That sounds like a plain bug. > >> - That's it, screw it; I'm out. > > >> Bottom line, if your site is not hacked (which wouldn't surprise me at > >> all after all these red flags), it's horribly broken. Apologies for > >> the rant. Thank you for taking the time to write it down a give us a chance to improve the user experience of occasional contributors. We added a ticket for it :) See https://www.logilab.org/ticket/103676 > >> but It's ridiculous to have to go through all this BS in 2012, > >> when for most other projects I would have forked them, pushed my > >> patch and made a pull request in less time than it took me to > >> figure out how am I supposed to contribute to pylint. I suppose you mean "if pylint was hosted at github". If you have time to search the archives of python-projects with Google Search (site:lists.logilab.org pylint contribute), you'll find http://lists.logilab.org/pipermail/python-projects/2011-August/003039.html and http://lists.logilab.org/pipermail/python-projects/2012-February/003165.html that point to https://bitbucket.org/nchauvat/pylint-patches/ and http://www.logilab.org/blogentry/100364 and http://selenic.com/pipermail/mercurial/2012-February/041644.html The former (patch repository at bitbucket) is used by regular contributors, such as http://lists.logilab.org/pipermail/python-projects/2012-May/003208.html The latter (mercurial evolve extension) is now used daily at Logilab and hopefully will soon spread among Mercurial enthusiasts of the early-adopters type. Thank you again for taking the time to describe your UX-bug. We will try to address it shortly. I hope to have convinced you we do not live in the past running antiquated software, we live in 2012 and develop free software to be used for the years to come. Regards, -- Nicolas Chauvat logilab.fr - services en informatique scientifique et gestion de connaissances _______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org http://lists.logilab.org/mailman/listinfo/python-projects
