Subject: Re: Nessus 3.0's failed community
From: Jamie Lokier <>
Date: Wed, 30 Nov 2005 19:39:13 +0000

Michael Bernstein wrote:
> He is told fooCo company policy is to get answers to his questions
> by asking co-workers instead.

Isn't that one of the main reasons for hiring someone though?  So that
they can form a more tightly knit team with foo's other developers -
and engage in more direct, rapid, whatever communication to get the
development job done?

And even if it's not official company policy, wouldn't the person tend
to chat with his new co-workers instead of asking on the lists, once
he's actually got co-workers who are knowledgable about the product,
and who have a better sense of his employer's priorities?

It seems near-inevitable that forming a tightly knit development team
for the efficiency improvements will reduce the visibility of their
communication to 'outsiders', as well as the ability of 'outsiders' to
be involved.  Forcing them to communicate through the mailing lists
(etc.) instead of chatting neighbourly (or over IM if remote), would
seem to be slowing down their communication in order to retain the
connection with people further from the core team.

That happens in tightly knit, non-commercial, open source teams after
all.  Ever noticed how the people who physically get together at Linux
kernel developer conferences seem to put together designs that folks
on the linux-kernel mailing list, many of whom couldn't afford the
travel, time or ticket fee, only see the results of?

-- Jamie