Hello Thorsten, Le Wed, 19 May 2010 13:42:26 +0200, Thorsten Ziehm <thorsten.zi...@sun.com> a écrit :
> > Hi Charles, > > we are at a point where we repeat our statements again and again. > So it doesn't make sense for me to answer on all of your comments > in your last mail. I can write, that evaluation of issues takes a lot > of resources in the OOo project (QA and DEV), that a lot of this > work is done by community members by Sun/Oracle ... but I hope > the QA process on OOo is known by you. Yes, although I'm by no means an expert. I do know two things in this discussion though: - You refuse to come to a compromise. - You do not wish to consider the need for an improvement of the quality of OOo (regardless of how OOo has been built) and does not accept the collaboration with others because in your own words it would cost too much. > > I want to summarize my statements only : > I couldn't accept (as a member of the QA project on OOo) that we > have to spend resources of the OOo project to making QA* in OOo > derivatives which doesn't spend resources for this project and > which doesn't contribute their code. See Thorsten Behrens's answer on this particular point. I would however like to add that the Ubuntu maintainers do not modify OOo, therefore *they cannot contribute back* since they are downstream distributors. So this is not a different product, but as you said, let's not continue to state our positions. > The resources will be missing > for making Quality Assurance for the OOo (vanilla) and will lead > to a worser quality of all OOo derivatives. This isn't acceptable > for me, perhaps for you too. It certainly would not be acceptable for me as well, but I feel your assessment of the amount of resources needed to evaluate incoming issues is somewhat overstated and does not take into account actual volunteers and perhaps the influx of these volunteers if we were to open up the IZ. > > I know the users of OOo on Linux are in conflict. They do not know, > which OOo they get. Each Linux derivative brings an own build of OOo > and all of them have different qualities and feature sets. So the > problem can be solved by using vanilla OOo for all of them. But as > I know this isn't wanted by the Linux distros. > > For me it isn't acceptable to make QA for other products (with the > name OOo) only, why the QA project have a process and know how to > deal with issues. You do realize -I need to make that clear here- that we went to the Ubuntu folks and told them to use the vanilla build. But they refuse to do so because it creates a lot of problems for them. And in fact, it creates more problems for them to use the vanilla build, as much as I would want them to use it, than to work with us on a common bugtracker. > > When you want to address the OOo commodity (all OOo products under > one roof) you should address this as CC member in the council. First, I would like to ask the opinion of the QA project leads. Charles. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qa.openoffice.org For additional commands, e-mail: dev-h...@qa.openoffice.org
