Hi Thorsten, Dieter, all,
Thorsten Behrens wrote:
[...]
While I definitely applaud all efforts spend improving performance
of OOo, I see serious overlap in scope with existing projects.
You're right, Thorsten, we don't need parallel work in different projects.
But I hope, this might be able to be avoided.
As performance is quite a crucial point of OpenOffice.org I think it is
a good idea to keep an eye especially on that topic - independent from
the different developer projects, but in tight contact to them.
[...]
Ultimately, I believe development work is already fragmented enough
with the existing number of projects, so I'd suggest stripping down
the scope to measuring performance (as QA-ing performance again
seriously overlaps with the QA project).
Perhaps it might be possible to modify the scope from
"Members of the project will improve the performance in
these areas,"
to
"Identified areas with insufficient performance will be worked on
together with the dedicated projects for these areas."
Same with QA - setting up a test case for performance testing is great.
It might be included in the QA testing routine afterward.
This would mean that developer interested in performance optimization
work will have to subscribe to more than one mailing list (depending on
the part of OOo they work on). I don't know if this is a problem for
some of them - but the Performance project will only be able to come
into life and stay alive if it can be seen as binding link between the
projects.
It will become an incubator project, so we'll have time to see how it
works before it becomes an official project. This is IMHO the idea of
incubator projects: Find out if it works better than before. If it does,
it might become an official project, if not, go back to the previous status.
Best regards
Bernhard
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
