Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index

On 2010-10-04 4:27 PM, Christoph Noack wrote:
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 ...

How about creating a single 'collaberation' list, that only accepts
messages from designated members of the other lists (we could use
volunteers for this), and these designated 'collaberators' wouild be
responsible for sending messages to the 'collaberation' list to notify
everyone that a conversation that affects one or more of the others is
occurring on whatever the other list is - then someone could go read
that thread and comment or take whatever action is appropriate.

The collab list could require [TAGS] in the subject, one [TAG] for each
of the other lists.

This way developers could just be members of their respective list, and
the collab list, and (using filters on the [TAGS] easily monitor issues
on the collab list that pertained to them...

Just a rough idea, but maybe could be made to work...?


Best regards,

To unsubscribe, send an empty e-mail to
All messages you send to this list will be publicly archived and cannot be deleted.
List archives are available at


Privacy Policy | Impressum (Legal Info) | Copyright information: 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.