On Oct 12, 2011 9:12 AM, "Anthony Liguori" <aliguori(a)us.ibm.com&gt; wrote: moving the project planning and future board meetings to IRC? posted in a public archive. It's significantly easier for many folks to participate in IRC meetings. with using IRC. Using IRC for regular meetings certainly doesn't preclude having occasional phone calls if necessary. +1

* Anthony Liguori (aliguori(a)us.ibm.com) wrote: The only other downsides I've heard voiced (having just gone through this debate elsewhere): 1) typing == slow for some folks 2) inevitible overlapping conversations 3) more consuming than phone (harder to do 2 things at once) 4) can't do from airport/kitchen/car/... thanks, -chris

On 10/12/2011 10:11 AM, Anthony Liguori wrote: +1, I share cdub's concerns that he pointed out but at the same time I think we can make it work :)

On Wed, Oct 12, 2011 at 08:04:19AM -0700, Chris Wright wrote: Yep, totally understand where this list comes from, I've been there before. The place I draw the line is, a tightly integrated team - such as a developer team at a company - has a higher importance on certain factors that make the above objections more relevant: * It's your team meeting at your JOB, you make the meeting no matter what. So it's key to have it highly available (call from anywhere) v. text-based. * The rest of your company may not be familiar with the pace of open source development - it doesn't respond to "NOW!" the way a job-role does, the urgency to be in meetings isn't the same, etc. * And so forth. Where it comes to open community meetings, we are plainly just more flexible to be as accommodating as possible. So this means we do IRC in plain text because: * It's easier for non-native English speakers. * In fact, some people can read English but not understand all the spoken accents. * It's translatable. * It's accessible - if you can't hear a phone conversation, you can read an IRC log. If you can't read a log, you can use a screenreader. * It's searchable when the log is archived. Once a project is out in the open and WANTS participation, that's when the phone calls stop and IRC+email begins. - Karsten -- name: Karsten 'quaid' Wade, Sr. Community Gardener team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41

On 10/12/2011 11:04 AM, Chris Wright wrote: let's keep the sync call until we are launched at the workshop. I expect that we will transition the board business to the mailing list and then only formally meet less frequently once most of the business is conducted on the list. The main reason for a call until launch is to deal with the sync and coordination. I expect that we can move to IRC/ mail list for 95+% of the business after the workshop Carl.

On 10/19/2011 08:33 AM, Robyn Bergeron wrote: Robyn, We need to keep the call this week and next. I want to make sure we are well coordinated coming up to the workshop. regards Carl