5:11 p.m.
This came up in today's project planning meeting. How do folks feel about
moving the project planning and future board meetings to IRC?
The advantage of IRC meetings are that the full meeting minutes can be posted in
a public archive. It's significantly easier for many folks to participate in
IRC meetings.
I think the only downside would be if anyone involved is uncomfortable with
using IRC. Using IRC for regular meetings certainly doesn't preclude having
occasional phone calls if necessary.
Regards,
Anthony Liguori
5:47 p.m.
On Oct 12, 2011 9:12 AM, "Anthony Liguori" <aliguori(a)us.ibm.com> wrote:
This came up in today's project planning meeting. How do folks feel about
moving the project planning and future board meetings to IRC?
The advantage of IRC meetings are that the full meeting minutes can be
posted in a
public archive. It's significantly easier for many folks to
participate in IRC meetings.
I think the only downside would be if anyone involved is uncomfortable
with using
IRC. Using IRC for regular meetings certainly doesn't preclude
having occasional phone calls if necessary.
+1
Regards,
Anthony Liguori
_______________________________________________
Board mailing list
Board(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/board
5:58 p.m.
* Anthony Liguori <aliguori(a)us.ibm.com> [2011-10-12 09:14]:
This came up in today's project planning meeting. How do folks
feel about
moving the project planning and future board meetings to IRC?
The advantage of IRC meetings are that the full meeting minutes can be
posted in a public archive. It's significantly easier for many folks to
participate in IRC meetings.
I think the only downside would be if anyone involved is uncomfortable with
using IRC. Using IRC for regular meetings certainly doesn't preclude
having occasional phone calls if necessary.
+1
Do we have a irc bot for logging?
Regards,
Anthony Liguori
_______________________________________________
Board mailing list
Board(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/board
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh(a)us.ibm.com
1:28 a.m.
On Wed, Oct 12, 2011 at 09:58:36AM -0500, Ryan Harper wrote:
* Anthony Liguori <aliguori(a)us.ibm.com> [2011-10-12 09:14]:
> This came up in today's project planning meeting. How do folks feel about
> moving the project planning and future board meetings to IRC?
>
> The advantage of IRC meetings are that the full meeting minutes can be
> posted in a public archive. It's significantly easier for many folks to
> participate in IRC meetings.
>
> I think the only downside would be if anyone involved is uncomfortable with
> using IRC. Using IRC for regular meetings certainly doesn't preclude
> having occasional phone calls if necessary.
+1
Do we have a irc bot for logging?
Putting up a 'meetbot' instance is on my list right after
gerrit/jenkins.
If we move meetings to IRC ... which I +1 btw ... we'll have the bot
in channel before the first meeting. :D
- Karsten
--
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture & Leadership
uri: http://communityleadershipteam.org
http://TheOpenSourceWay.org
gpg: AD0E0C41
6:04 p.m.
* Anthony Liguori (aliguori(a)us.ibm.com) wrote:
This came up in today's project planning meeting. How do folks
feel about
moving the project planning and future board meetings to IRC?
The advantage of IRC meetings are that the full meeting minutes can be
posted in a public archive. It's significantly easier for many folks to
participate in IRC meetings.
I think the only downside would be if anyone involved is uncomfortable with
using IRC. Using IRC for regular meetings certainly doesn't preclude having
occasional phone calls if necessary.
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
6:45 p.m.
On 10/12/2011 10:04 AM, Chris Wright wrote:
* Anthony Liguori (aliguori(a)us.ibm.com) wrote:
> This came up in today's project planning meeting. How do folks feel about
> moving the project planning and future board meetings to IRC?
>
> The advantage of IRC meetings are that the full meeting minutes can be
> posted in a public archive. It's significantly easier for many folks to
> participate in IRC meetings.
>
> I think the only downside would be if anyone involved is uncomfortable with
> using IRC. Using IRC for regular meetings certainly doesn't preclude having
> occasional phone calls if necessary.
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
I think the key is to moderate the discussion and make sure there's a clear agenda.
Regards,
Anthony Liguori
3) more consuming than phone (harder to do 2 things at once)
4) can't do from airport/kitchen/car/...
thanks,
-chris
1:43 a.m.
On Wed, Oct 12, 2011 at 08:04:19AM -0700, Chris Wright 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/...
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
9:07 a.m.
On 2011-10-13 6:43, Karsten Wade wrote:
On Wed, Oct 12, 2011 at 08:04:19AM -0700, Chris Wright 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/...
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.
+1 and add one moe
* It is easy to know who is talking in the meeting by IRC ID, especially
for a meeting with many attendees.
Once a project is out in the open and WANTS participation, that's when
the phone calls stop and IRC+email begins.
- Karsten
_______________________________________________
Board mailing list
Board(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/board
8:01 p.m.
On 10/12/2011 10:11 AM, Anthony Liguori wrote:
This came up in today's project planning meeting. How do folks
feel
about moving the project planning and future board meetings to IRC?
The advantage of IRC meetings are that the full meeting minutes can be
posted in a public archive. It's significantly easier for many folks to
participate in IRC meetings.
I think the only downside would be if anyone involved is uncomfortable
with using IRC. Using IRC for regular meetings certainly doesn't
preclude having occasional phone calls if necessary.
+1, I share cdub's concerns that he pointed out but at the same time I
think we can make it work :)
3:33 p.m.
On 10/12/2011 07:11 AM, Anthony Liguori wrote:
This came up in today's project planning meeting. How do folks
feel
about moving the project planning and future board meetings to IRC?
The advantage of IRC meetings are that the full meeting minutes can be
posted in a public archive. It's significantly easier for many folks
to participate in IRC meetings.
I think the only downside would be if anyone involved is uncomfortable
with using IRC. Using IRC for regular meetings certainly doesn't
preclude having occasional phone calls if necessary.
Regards,
Anthony Liguori
Since we've had this discussion over the past week, I've added it to
today's sync call agenda. It seems like we have a number of people in
favor of the idea, but I figured it's probably best to continue with the
call for this week, and come to a solid, announced conclusion/decision,
before shifting to IRC (if in fact that is what's agreed-upon.)
We should also double check to make sure everyone on the call is
familiar with IRC, and get a bot in #ovirt (or #ovirt-meeting) if
necessary. (Though, IMO, it's helpful to have a bot in channel,
regardless - it's nice to be able to capture spontaneous discussions
with meetbot.)
-Robyn
4780
days inactive
4787
days old
9 comments
8 participants
participants (8)
-
Anthony Liguori -
Chris Wright -
Dustin Kirkland -
Karsten Wade -
Perry Myers -
Robyn Bergeron -
Ryan Harper -
shu ming