On Tue, Jan 13, 2009 at 05:53:45PM +0100, Mathias Bauer wrote: > In fact we had a kind of "virtual performance project", consisting of > all the people that at times worked on that matter. But the outcome of > that occasional work was quite low, it was neither planned nor focussed. > I'm confident that this will change with giving performance a higher > visibility and by assigning a real, existing (not only "virtual") team > to it. > Hi Mathias,
you're arguing for something I didn't question at all (planned, focussed work on performance, visible outcomes; and for actually assigning people to that task - I'm all with you there). Having a dedicated CollabNet project by no means implies anything of the above (as you correctly asserted via the ui project example) - not much (any?) arguments in favor of that, only blank "+1" votes for a proposal that mixes those two topics... ;) Could we get to the core of this, in which way does a segregate CollabNet project further any of your mentioned goals (in comparison to still having a team of people do focussed work on performance, but using the established OOo mailinglists etc.)? Cheers, -- Thorsten --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
