I'm echoing a recent blog by Sylvain (http://www.logilab.org/blogentry/10055):
After several months with no time to fix/enhance pylint beside answering email and filing tickets, I've finally tackled some tasks yesterday night to publish bug fixes releases ([`1`_] and [`2`_]). The problem is that we don't have enough free time at Logilab to lower the number of tickets in pylint tracker page_ . If you take a look at the ticket tab, you'll see a lot of pendings bug and must-have features (well, and some other less necessary...). You can already easily contribute thanks to the great mercurial_ dvcs, and some of you do, either by providing patches or by reporting bugs (more tickets, iiirk ! ;) Thank you all btw !! Now I was wondering what could be done to make pylint going further, and the first ideas which came to my mind was : * do ~3 days sprint * do some 'tickets killing' days, as done in some popular oss projects But for this to be useful, we need your support, so here are some questions for you: * would you come to a sprint at Logilab (in Paris, France), so you can meet us, learn a lot about pylint, and work on tickets you wish to have in pylint? * if France is too far away for most people, would you have another location to propose? * would you be on jabber for a tickets killing day, providing it's ok with your agenda? if so, what's your knowledge of pylint/astng internals? .. _`1`: http://www.logilab.org/project/pylint/0.18.1 .. _`2`: http://www.logilab.org/project/logilab-astng/0.19.1 .. _page: http://www.logilab.org/project/pylint/ .. _mercurial: http://www.selenic.com/mercurial/ -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science _______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
