On Thu, Mar 1, 2012 at 12:41 PM, Samuli Seppänen <sam...@openvpn.net> wrote: > 1) Preliminary topic list is sent to openvpn-devel ml > 2) The actual meeting (fully open) > 3) The meeting summary + complete chatlog is sent to openvpn-devel ml > > The idea was to minimize the negative impact of the meetings as much as > possible. Also, we haven't had that many meetings in a long while: > > <https://community.openvpn.net/openvpn/wiki/IrcMeetings> > > The dangerous aspect of the IRC is it's more personal nature, and the > fact that it's far quicker to get feedback from there than from the > mailing list. The problem is that only a subset of developers and > community members hang out on the IRC. This is fine, as long as the > people on the mailing lists are not excluded from the discussion. This > is where we need to be really careful and not get too comfortable on the > IRC channel.
The problem is with the "Meeting Summary"... It breaks the discussion. Let's say you have discussion on topic XXXX, this thread has 10 messages. Then there is a "Meeting Summary" where XXXX is discussed. Then you continue to discuss the XXXX as reply to the "Meeting Summary" or in entirely different thread. As a result you may loose the people discussing XXXX. And you lose the history of discussion XXXX, as you need to go and look in many threads and instances. If IRC tool is used, it should be used as a proxy. Each summary should be replied to the designated thread to allow proper asynchronous communication without breaking the sequence because of a synchronous meeting. If James has problems with reading mails, you can discuss with him any subject but again reply to the appropriate thread to avoid breaking the sequence. Reading IRC logs is way out of valid request... Just my two cents. Alon.
