> -----Original Message----- > From: Jürgen Schmidt [mailto:jogischm...@gmail.com]
> This would be a very interesting approach that of course is indeed not > completely new. If we wouldn't have useful patches in BZ I personally > would of course support such an approach. Having a clean and fresh BZ > would be an opportunity to focus the real problems we have and find a > good balance between feature development and bugfixing. > > But of course it's not really realistic :-( > > The main problem with votes at the moment is that we don't > have a common > understanding how to handle issue with votes. I would say at > the moment > these votes are useless. We had focused on issue with high > votes in the > past because it was the goal for developers at this time, managers > pushed it but later on the priorities changed again and nobody really > took care of these issues. > > If we want to make use of this BZ feature we should first > think what we > want to do with this issues and can we do it. Means we can't force > developers to work on such high voted issues, we can only motivate to > focus on these issues first. Or if some sponsors are interested to pay > developers to work on such issues that could also work, I don't know. There are certainly technical problems or problems of coordination, but what we need, first and foremost, is the insight that we need to talk with users so that they understand us. Let me be clear: our internal problems are users not care, they want a working software. Where users give us Feadback, (for example write issues) they want something in return for it, that we look seriously at their Feadback. If our response should be to this user that we can not help them, because we do not agree on how to deal with issues or votes, then that is unfortunately insufficient. This is not an accusation but only the truth, and we should do everything to overcome these problems quickly. > In general I think we should continue the discussion about > our long term > goals for the project and the product first. We can't do > everything and > it is important that we at least have all some common understanding > about our strategy. > > We can start with thinking what office productivity suite really means > and if we already fulfill these requirements... Good, then I will begin by saying: the interests of our users should be our most important goal. The minimum of this is we listen to their problems and take it seriously. AOO is not software experts, but for normal users and normal users want normal responses. Please let us understand together, that this is an important difference to the Apache Web server (for example), as this is a software mainly for experts, AOO, but for normal users. Greetings, Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
