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 > > > > See issue 125954 as an example -- > > https://issues.apache.org/ooo/show_bug.cgi?id=125954 > > > > So far I have found 6919 issues for ENHANCEMENTS regardless of status. > > None of them are RESOLVED, so my assumption is that a negative > > recommendation doesn't get any special status handling. > > > > Should we make an attempt to go through the old ENHANCEMENT/FEATURE > > issues and see if we can "finalize" the ones that have been turned down > > by some means -- RESOLVED/NOT AN ISSUE -- or ?? > > > > -- > > ------------------------------------------------------------------------- > > MzK > > > > "An old horse for a long, hard road, > > a young pony for a quick ride." > > -- Texas Bix Bender > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
