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, Charles -- To unsubscribe, send an empty e-mail to [email protected] 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/
