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.
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. 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.
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.
When you want to address the OOo commodity (all OOo products under
one roof) you should address this as CC member in the council.
Thorsten
* : making QA does also mean to evaluate incoming issues and that's
bind a lot of resources
[...]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
