1 |
Donnie Berkholz wrote: |
2 |
> On 14:05 Fri 13 Mar , Michael Higgins wrote: |
3 |
>> Even if they are, an IRC log is a *terrible* way to document an issue. |
4 |
> |
5 |
> I agree. So is a mailing-list archive that is also never summarized. |
6 |
> It's not the location that makes it a problem, it's the volume of |
7 |
> information and the lack of a summary of important decisions or long, |
8 |
> important discussions. |
9 |
> |
10 |
|
11 |
I certainly don't consider the use of IRC harmful per-se or consider it |
12 |
a "cabal," but I can't consider IRC and an unsummarized mailing list |
13 |
equivalent communication mediums. |
14 |
|
15 |
If I want to know what is going on in IRC I need to leave a client |
16 |
connected 24x7 (and if my connection goes down for whatever reason I |
17 |
just miss whatever happens). Then I need to read through thousands of |
18 |
lines of banter to see what is going on. |
19 |
|
20 |
If I want to know what is going on in a mailing list I launch my |
21 |
threaded email client. If a computer goes down SMTP, IMAP, and various |
22 |
redundant servers will eventually get the messages to me. The |
23 |
discussion is threaded and categorized by topic, so I can mercilessly |
24 |
hit delete and not have much risk of missing something I'm interested |
25 |
in. Essentially even an "unsummarized" mailing list is fairly well |
26 |
summarized compared to IRC. |
27 |
|
28 |
Don't get me wrong - I like the team-building aspects of IRC. However, |
29 |
it is not a good communication medium when you're dealing with |
30 |
volunteers that might only spend a few hours per week total working on |
31 |
Gentoo (or maybe only a few hours per month), spread across 24 time |
32 |
zones. It is perfect for realtime collaboration on solving specific |
33 |
problems. It is also great for brainstorming ideas, and just having |
34 |
fun. Unfortunately, it also shares certain drawbacks with the phone - |
35 |
for starters it tends to prioritize tasks by urgency rather than by |
36 |
importance. It also encourages "shooting from the hip" - just like |
37 |
having meetings without an agenda, pre-discussion, and general |
38 |
preparation. No problem for trivial tasks, but not a good idea when |
39 |
making final decisions of strategic importance. |
40 |
|
41 |
However, if certain work takes place exclusively on IRC then you're |
42 |
going to exclude some people. Many of those people could be strong |
43 |
contributors but they might not like working in "realtime." This might |
44 |
not be because of communication skills/etc - maybe they have a family |
45 |
and they'd rather see what needs to be done and take care of it here and |
46 |
there without being given an assignment and having 10 other people |
47 |
bugging them about whether it is done yet when they have 14 other things |
48 |
to do. Sure, such a dev is probably not a good candidate to be leading |
49 |
a major Gentoo project, but that doesn't mean that they have little to |
50 |
contribute. For example, I typed this email in one sitting but I could |
51 |
have just as conveniently taken 3 days to piece it together in 5 minute |
52 |
bursts. |
53 |
|
54 |
I'd consider the current council format a good example of how IRC can be |
55 |
used in conjunction with mailing lists, agendas, and scheduled meeting |
56 |
times. IRC can be used to finalize thinking and make decisions. It can |
57 |
also be used for informal discussion anytime before a meeting. Much of |
58 |
the serious contribution is captured on mailing lists, however, and when |
59 |
decisions are made it is based upon the widely-gathered input. |
60 |
Everybody knows what decisions are going to be made in advance and can |
61 |
show up if desired. If they can't show up they can at least contact |
62 |
council members in advance (and the world at large) to state their |
63 |
opinions. This certainly doesn't need to be used for every tiny Gentoo |
64 |
decision - but it is a great model for how to handle things of importance. |