On Wed, Sep 22, 2010 at 1:47 PM, Antoine Pitrou <solip...@pitrou.net> wrote: > > Simply, situations like the above (Mark closing a bug just because > nobody would answer his message on a short delay) have happened > multiple times - despite people opposing, obviously -,
I must say that the same attitude is present in meta tracker proposals as well. People, who "need a closure" quite often tend to mark issues (enhancement proposals) as won't fix just because they can't (or don't want) to see solution or just because they think that solution is too complicated to implement. They judge it from the point of annoyed developer even though the feature can actually be handy for users of the tracker. The reason here could be that developers are lost in the amount of issues and can't filter them and see who does what. For example, I could triage issues for some modules I am interested in, but I can't. So, to overcome the complexity of global bug space developers are tempted to squash confusing issues. There can be only one solution - concentrate on the tools. Add an "omnibox" to tracker that will use autocompletion and labels (Google Code). Useful ticket query interface (Trac). Favorite issues (Google stars). Personal tags, issue sets, message filters (Slashdot). I've already brought the issue about necessity to enhance Python tools some six months ago. At that time Richard Leland promised to do a research of Python process to further work on proposal to improve it. This was due to June, but still no result. I should blame myself for waiting, because I had some plans to propose, but at that time it was impossible to get going, because everybody had big hopes for that research. > There was a whole python-dev thread some time (weeks? months?) ago where > several of us already tried to suggest more fruitful ways of > contributing, suggestions which weren't received very welcomingly AFAIR. This will never give any results if you did not collecting the outcomes, summaries and links for the future. My vision is that other fruitful ways of contributing are not fun. The most "modern" tool with more or less sane gameplay here is tracker. But it suxx in many ways. Mostly because it is too old and too few are able to patch it due to either lack of information or experience (or time to get one or another). Mercurial is insane, and there isn't really anything else (except Sphinx). Well, there are lists, but there is nothing you can really do about them (except prevent Mailman from dropping archives from time to time or setup a Google Groups mirror). -- anatoly t. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
