[Top] [All Lists]

Re: Prism54 Driver Project Complete

To: Jeff Garzik <jgarzik@xxxxxxxxx>
Subject: Re: Prism54 Driver Project Complete
From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxxxxxxxxxxxx>
Date: Tue, 16 Mar 2004 01:38:56 -0500
Cc: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxxxxxxxxxxxx>, prism54-devel@xxxxxxxxxxx, netdev <netdev@xxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, jgarzik@xxxxxxxxxx
In-reply-to: <>
Mail-followup-to: Jeff Garzik <jgarzik@xxxxxxxxx>, "Luis R. Rodriguez" <mcgrof@xxxxxxxxxxxxxxxxxxxx>, prism54-devel@xxxxxxxxxxx, netdev <netdev@xxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, jgarzik@xxxxxxxxxx
Organization: Rutgers University Student Linux Users Group
References: <> <>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.28i
On Tue, Mar 16, 2004 at 01:01:31AM -0500, Jeff Garzik wrote:
> 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

Well in that case we'll also act as the "official" prism54 patch
recipients/senders. And by "we" I mean any of the prism54 developers
listed on our project page. We can do this but we can only do this if the
patches are sent to *us* based on clean bk trees. It's important that
patches are sent to *us* prior to inclusion in the kernel since this
driver is not the normal 1-file driver. If a patch goes into the driver
in the kernel tree but not ours it's going to be a pain mantaining our
tree / writing patches for you (as was done just now), specially since
we're still a heavily active driver project. 

So for now then, I'm going to update our CVS repository to match the
kernel tree and we'll soon send you patches with the latest changes.
Please only accept then patches/changes for the driver if its passed through us 
this is possible). It's not that that we don't want people to contribute
it's just that this is the way it has to be in order to make our live's
easiers as mantainers of the driver.

I'm already subscribed to the netdev list and I'll keep my eyes open for
any wide-kernel changes/patches and apply them too. I'll ask the others
to do the same.

Is this an OK plan?

GnuPG Key fingerprint = 113F B290 C6D2 0251 4D84  A34A 6ADD 4937 E20A 525E

Attachment: pgpMnTkvhYz5e.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>