Venkata Krishnan wrote:
Typically these discussions have multiple aspects to it and we end up
bringing perspectives to each aspect. If there is such a topic then I'd
think the WIKI is a good place. There could be one description of the
problem and comments by the community at various points. So at any time one
knows what's the spine of the problem being discussed and to which aspect a
bunch of comments relate to. Ofcourse there will be mail that just about
summarizes the problem in about 5 lines and provides a link to the wiki
page. Maybe with every update the person updating could post back to the ML
an anchor to what as been added to the Wiki. My 2 cents.
Simon Nash wrote:
The point of my question was to ask what else we could do when email
isn't sufficient to resolve a difficult technical issue. I think we
have seen this happen a number of times, where a thread peters out with
no consensus or decision. I'd be interested in other views on this.
Some thoughts:
- Spawn threads for different topics, keep each thread specific
- Post short summary emails
- Document details on our Wiki in a developer section
- Use [VOTE] more often to make decisions?
- Let people implement alternatives, providing concrete ground for
discussion later?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
