From: Jeff Garzik <jgarzik@pobox.com>
To: "Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>
Cc: prism54-devel@prism54.org, netdev <netdev@oss.sgi.com>,
linux-kernel@vger.kernel.org, jgarzik@redhat.com
Subject: Re: Prism54 Driver Project Complete
Date: Tue, 16 Mar 2004 01:01:31 -0500 [thread overview]
Message-ID: <4056983B.9010609@pobox.com> (raw)
In-Reply-To: <20040316055249.GE24063@ruslug.rutgers.edu>
There still needs to be a central "maintainer" of prism54, someone who
sends patches either directly to me, or via Jean to me (maintainer's
choice). Ideally, it is best to funnel patches from everybody through
driver-maintainer -> subsystem maintainer -> Marcelo|Andrew|Linus. That
only breaks down when the driver or subsystem maintainer is too slow,
and doesn't follow the "release early, release often" precept :)
Open source is about lack of control, and trusting that community and
consensus will produce superior software over the long run... but lack
of control doesn't mean lack of organization :)
Jeff
next prev parent reply other threads:[~2004-03-16 6:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 5:52 Prism54 Driver Project Complete Luis R. Rodriguez
2004-03-16 6:01 ` Jeff Garzik [this message]
2004-03-16 6:38 ` Luis R. Rodriguez
2004-03-16 6:53 ` Jeff Garzik
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=4056983B.9010609@pobox.com \
--to=jgarzik@pobox.com \
--cc=jgarzik@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@studorgs.rutgers.edu \
--cc=netdev@oss.sgi.com \
--cc=prism54-devel@prism54.org \
/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;
as well as URLs for NNTP newsgroup(s).