From: "Jay Carlson" <nop@nop.com>
To: "Eric Watkins" <watkinse@attens.com>, <linux-mips@oss.sgi.com>
Subject: Re: Status reports?
Date: Thu, 29 Jun 2000 07:46:01 -0400 [thread overview]
Message-ID: <019501bfe1bf$99746b10$0a00000a@decoy> (raw)
In-Reply-To: 001c01bfd6f7$536705b0$540ed7c0@hq.sd.cerf.net
"Eric Watkins" <watkinse@attens.com> writes:
[...]
> I know lots of this information gets distributed via IRC but someone
should
> let everyone, who's not on IRC all the time, know what's going on and what
> progress is being made.
IMO this is a serious problem for many open source development projects
today. Much of the interaction occurs in IRC or instant message chats, and
not in email. The people who are participating in the online chats have
much better coordination, but it ends up excluding a lot of people. It's
not just people in the wrong timezone who lose out---projects also lose the
potential effort of people who join the mailing list, see nothing going on,
and don't get a chance to help. I've found that even casual readers of a
mailing list can bring insight from other projects to bear on problems.
Jay
WARNING: multiple messages have this Message-ID (diff)
From: "Jay Carlson" <nop@nop.com>
To: Eric Watkins <watkinse@attens.com>, linux-mips@oss.sgi.com
Subject: Re: Status reports?
Date: Thu, 29 Jun 2000 07:46:01 -0400 [thread overview]
Message-ID: <019501bfe1bf$99746b10$0a00000a@decoy> (raw)
Message-ID: <20000629114601.MhXWIw0MggmZLYkYiLJrj7GbM-WwyNk8o2ryq8jLRe4@z> (raw)
In-Reply-To: 001c01bfd6f7$536705b0$540ed7c0@hq.sd.cerf.net
"Eric Watkins" <watkinse@attens.com> writes:
[...]
> I know lots of this information gets distributed via IRC but someone
should
> let everyone, who's not on IRC all the time, know what's going on and what
> progress is being made.
IMO this is a serious problem for many open source development projects
today. Much of the interaction occurs in IRC or instant message chats, and
not in email. The people who are participating in the online chats have
much better coordination, but it ends up excluding a lot of people. It's
not just people in the wrong timezone who lose out---projects also lose the
potential effort of people who join the mailing list, see nothing going on,
and don't get a chance to help. I've found that even casual readers of a
mailing list can bring insight from other projects to bear on problems.
Jay
next prev parent reply other threads:[~2000-06-29 11:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-15 18:27 Status reports? Eric Watkins
2000-06-15 18:27 ` Eric Watkins
2000-06-29 11:46 ` Jay Carlson [this message]
2000-06-29 11:46 ` Jay Carlson
2000-06-29 16:18 ` Eric Watkins
2000-06-29 16:18 ` Eric Watkins
2000-06-29 16:29 ` Richard
2000-06-30 0:39 ` Ralf Baechle
2000-06-29 17:38 ` Ian Chilton
2000-06-29 17:38 ` Ian Chilton
2000-06-29 22:51 ` rob
2000-07-01 23:23 ` Jay Carlson
2000-07-01 23:23 ` Jay Carlson
2000-07-04 18:21 ` Robert Current
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='019501bfe1bf$99746b10$0a00000a@decoy' \
--to=nop@nop.com \
--cc=linux-mips@oss.sgi.com \
--cc=watkinse@attens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox