I notice that there has been no further discussion about this and the requested guidance is not forthcoming.
I find the way incidents are handled on the AOO Bugzilla to be rather distressing, especially with the rapid closing and rebuffs to the submitters. I attempt to be more considerate by example although it is not something I have the capacity to accomplish one-handed. I have already requested that such issues be assigned to me instead of being abruptly closed. I must renew that request. One problem is that users see definite issues and they are rebuffed for not being expert reporters and not limiting their input to code defects. The categories in the Bugzilla are also brittle, not allowing us to recognize the broader conditions that may apply in the disposition of an issue report. There is also not much help in triage of defects and enhancement requests. Having a visible process might help users to understand what is necessary while honoring the effort they make to identify and demonstrate issues of concern to them. I don't like cross-posting, I am going to raise this separately on the dev-openoffice list as well. However the project has limited capacity at this time, I think this is a critical user-facing area that needs to be addressed. - Dennis -----Original Message----- From: Cem Kaner [mailto:[email protected]] Sent: Wednesday, January 28, 2015 07:38 To: [email protected] Subject: RE: how to close a non-recommended ENHACEMENT issue? I agree that it is useful to close bad recommendations. My role in this project is as a teacher whose students replicate/evaluate unconfirmed OOo bugs as one of their course requirements. Through this lens, I review maybe 100 bugs per year. It's a limited but nontrivial sample. I have the concern that sometimes it seems that an active volunteer sometimes treats real bugs or legitimate suggestions as dumb ideas or old and settled issues. So there is the obvious process question: How does the line get drawn. But there is clearly stuff in the database that can be a distraction rather than a source of ideas for improvement. -- cem kaner > Date: Tue, 27 Jan 2015 18:30:06 -0500 > Subject: Re: how to close a non-recommended ENHACEMENT issue? > From: [email protected] > To: [email protected] > > On Tue, Jan 27, 2015 at 5:27 PM, Kay Schenk <[email protected]> wrote: > > What is the procedure for closing an ENHANCEMENT issue when the > > enhancement is not recommended? > > > > IMHO, the set of all open ENHANCEMENT issues comprise a "wish list" > which volunteer developers are welcome to dip into if they want. We > will always have more such enhancement requests than we can address. > This is true of every project. Only a dead project has no more ideas > for enhancement, > > But if an idea is objectively bad then we should probably close it. > For example, if it would break a standard, break another feature, > perhaps if it is redundant, etc. I recall reading about a survey > Microsoft did of Office 2003 users, asking them what features they > wanted added to Office. When the survey results were tallied they > found that many of the feature requests were already in the product, > but hard to find. > > Does this make sense? Just because no one has implemented a feature > yet does not mean the idea is a bad one. > > Regards, > > -Rob [ ... ] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
