Development issues part 1: Project communication [LWN.net]

Development issues part 1: Project communication

Posted Jan 10, 2008 8:28 UTC (Thu) by evgeny (guest, #774)
Parent article: Development issues part 1: Project communication

> The reverse is also true: the perceived slow pace of mailing-list only projects has the
effect of excluding those with a strong preference for a faster style of development. As
Raymond shows, though, there is hope that members of one school can retrain  if they wish 
for the other.

No, this is often not only the issue of will. It's related to the style of life. For a
majority of high-tech full-job occupations, IRC is impossible during the work hours. Of
course, DVCS and specialized bug-tracking software are OK.

(Log in to post comments)

Use of IRC

Posted Jan 21, 2008 23:12 UTC (Mon) by alex (subscriber, #1355) [Link]

Well it depends if it's part of your job. At my current place of work we have internal IRC
chat rooms for each project where it's not uncommon for someone to pop up and ask a question
about X and be pointed in the right direction. The use of trigger phrases and sounds mean you
don't actually have to read every line of dialog ever said.

Careful choice of IRC bots can also be useful. Once such hand crafted "multibot" provides a
great deal of useful script like functionality to all the engineers in the room at the same
time allowing idle observers to see stuff someone is looking at.