On 17 septembre 18:21, Huurne, Maarten ter wrote: > Hi, Hi Marteen > > 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 > > Speaking for myself here: I will be soon leaving the very Python intensive > project at Philips I'm in now and the next thing I will be working on does > not use Python. So I won't be able to convince my employer to spend time on > pylint. Since I don't have many holidays, I don't want to take time off for > it either. That leaves the weekend; I'm not sure if that is possible for the > Logilab people?
Convince your employer the only good thing is Python (tm) :) That said, I hope you'll still find some time for Python. And pylint of course ! Anyway, as explained in https://www.logilab.org/blogentry/18781, we'll start with a simple irc/jabber bug days. That would be great to see you there if you 've a few time. regards, -- Sylvain Thénault LOGILAB, Paris (France) Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services CubicWeb, the semantic web framework: http://www.cubicweb.org _______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org http://lists.logilab.org/mailman/listinfo/python-projects
