On Monday, 12 of May 2008, Jonathan Corbet wrote:very good idea ! anyhow, i`m browsing trough bugzilla for some time and try helping where i can and there is one thing which is really noticeable: there are bugreports not being worked on systematically enough and reporters often don`t feel welcome there. i saw bug reports which didn`t get a reply for a year or so. somebody excused for "posting so much" - all he did was posting a proper description of his problem. improving of bugzilla handling would be another incentive for bug reporter, imho. someone who reports a bug there and never gets a response (not even a formal "thanks for your report....") will probably never report again. i have worked for support (software product) some time ago and i learned one thing there: there needs to be someone to keep track of the users` input and to keep track of the developers action/response. bugreporters forget about their bug if they found a workaround (buying new hardware or whatever) and developers mostly prefer working on new code rather than fixing issues. that`s not true for ever user or developer, but if you really want bugs get fixed, someone acting as a mediator is essential. . regards roland --
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Srivatsa Vaddagiri | containers (was Re: -mm merge plans for 2.6.23) |
| Benjamin Herrenschmidt | Re: [linux-pm] [PATCH] Remove process freezer from suspend to RAM pathway |
git: | |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Patrick McHardy | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 6/7] [CCID-2/3]: Fix sparse warnings |
