On Mon, Mar 18, 2013 at 10:11 AM, RGB ES <rgb.m...@gmail.com> wrote: > 2013/3/18 Jörg Schmidt <joe...@j-m-schmidt.de> > >> >> >> > -----Original Message----- >> > From: Rob Weir [mailto:robw...@apache.org] >> >> > I'd say, "Thanks for the suggestion. We take all suggestions >> > seriously, and user suggestions are often the source of ideas that >> > make it into the product. Thank you for using AOO." >> >> Sounds fine for me. >> >> > The title of the tread is "A question about existing practices". I >> > think the facts are quite clear. If we have many 10 year old >> > untouched BZ issues then fixing these issues is not part of our >> > existing practice, whether you define that as mandatory, voluntary or >> > whatever. >> >> No problem. >> >> > "Practice" is what we do, not what we talk about doing. >> >> Yes, but what we must be as clearly defined this user can foresee it. >> >> Why? >> If I as a user know any bug in the program, it may be important for me to >> know _approximately_ when this will be fixed. >> >> > you want to argue that we talk a lot about fixing old issues, and say >> > many solemn things about how important they are, then I would agree >> > with you 100%. But we don't actually do anything about them. >> >> I do not know how to define something should, but I know that you have to >> make it transparent. >> >> For example, a road map for developing the program is important because it >> clarifies what new features AOO will have in the future. That's right, >> that's a good thing. >> >> But it is also important to clarify how to deal with bugs and feature >> wishes of users. >> There was the suggestion to delete all old votes, only we must still >> clarify how we handle new votes. I think. >> > > +1. > > There is an old joke: "I'm only responsible for what I say not for what you > understand", but the fact is that being AOO an end user application what > our users understand IS important for us. And what will people understand > if they know all those votes are being deleted? IMO, users will take this > as "they do not care about our votes, why should I vote again? Why should I > fill a bug report that nobody reads?" and that's a really bad thing. >
They'll believe what we tell them. If we say that we're "resetting" the vote counts in order to determine what is most relevant to users today, starting with an unbiased and fresh view of today's users priorities, and not to over-advantage the dead hand of decade-old votes from users who may or may not even still be using OpenOffice today, then this will be seen as a good thing. > If you want to know how relevant old issues are, once we have a working > survey system we can start a series of surveys about most wanted features > requests. IMO, the only valid way to delete votes, the only way that show > respect to our users is to close the corresponding issues. > The fact that there are decade old issues demonstrates that they are not relevant at all. I can't think of any test of irrelevancy more accurate than pointing out that they have been ignored for over 10 years. My suggestion was merely a way of getting feedback that might be more relevant. But that's fine. If we're more comfortable claiming that decade-old untouched issues are sacred to the project, then that's OK. They can just as easily be ignored for another decade. We have better means, like Google Moderator, or surveys, for finding out what users actually think today. -Rob > Just my 2¢ > > Regards > Ricardo > > >> >> >> Greetings, >> Jörg >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
