Am Montag, den 04.10.2010, 22:00 +0200 schrieb Volker Merschmann:
Ideally, I want QA folks to take notice if the Devs start debating
details of specific features, and conversely, I want Devs to take
notice of QA talking about specific "problem areas" in the product.
But you should also be aware that there are much qa-people which are
doing just testing.
These are not so "technical" and wouldn't like to read or even
understand the things on the dev-list. And there is much
organisational stuff around the testing which wouldn't interest the
Interesting discussion ... I think I do understand all your reasons,
although they aren't fundamentally different.
Same is true for a topic like UX (User Experience). You have to collect
material for UX, you have to discuss issues within UX, it is required to
kick-off activities from UX (e.g. collect tiny usability issues). But on
the other hand, it is extremely important to keep in touch with
development - to be consulted, to understand the other persons'
So I think we'll end up with different infrastructure bits for each of
the teams. But if it is about collaboration, we shouldn't be that far
away from each other - may it be working in small teams or being located
on the same mailing list.
Somehow, we have to bridge that gap ...
To unsubscribe, send an empty e-mail to email@example.com
All messages you send to this list will be publicly archived and cannot be deleted.
List archives are available at http://www.documentfoundation.org/lists/discuss/
- Re: [tdf-discuss] Re: [WEB] interim mailing list structuring - a proposal (continued)
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy