Hi, > 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? > * 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? I looked up the price of high-speed train tickets and they are quite affordable if booked long in advance. It is still a long trip though, so probably not worthwhile unless it's a multi-day sprint. > * if France is too far away for most people, would you have another > location > to propose? Maybe it could be a half/full day event at a multi-day open source or Python convention? > * would you be on jabber for a tickets killing day, providing it's ok > with your agenda? Maybe IRC is more convenient than Jabber? It would allow the whole group to see the questions and learn from the answers. You can create a channel on for example chat.freenode.net by simply joining the new channel (a channel exists because someone is there). I think this method would be the most convenient for me, since I could do it a single day without having to travel. > if so, what's your knowledge of pylint/astng internals? I can find my way around in pylint, but I have trouble understanding the details of astng. Bye, Maarten The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message. _______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org http://lists.logilab.org/mailman/listinfo/python-projects