[arch-dev-public] Driver Maintainers
roman.kyrylych at gmail.com
Fri May 11 14:47:22 EDT 2007
2007/5/11, Aaron Griffin <aaronmgriffin at gmail.com>:
> On 5/11/07, Alexander Baldeck <kth5 at archlinuxppc.org> wrote:
> > Hey all,
> > as you may have noticed I picked up X.org from Jan to take some load off
> > of his shoulders. I'm very proficient in doing the whole X.org thing
> > since I've done so over a phase of like 3 years in a professional
> > environment.
> > Then again, testing quickly became a problem. I can't possibly come up
> > with all the hardware to actually more than just build-install-test most
> > in x11-drivers. I would suggest that we assign TUs who have these
> > chipsets as testers or even maintainers. We could even drive this
> > further with other packages where we didn't do so yet:
> > * lirc
> > * madwifi
> > * wlan-ng
> > aso.
> > It would further go into the direction of packaging divisions and raise
> > quality of our packages. Opinions? Ideas how this can be implemented
> > without changing our system to much and everybody still being fine with it?
> I like the idea of having a group of "testers" for hardware stuff.
> To get the ball rolling, perhaps we could start a simple wiki page
> where a user can come in and list the hardware and arch packages they
> use that may be unique - we can figure out a plan of attack while
> gathering this data.
Yeah, I've brought this on some time ago too after finding that dead
page on devwiki.
Also, it will greatly help in cases when confirmation of a bug is needed.
> For right now, I'd say lets only as TUs and devs for information, just
> to ensure some chain-of-command remains.
> Here's a random idea (and part of the original reason too) - The
> "hidden" arch-commits list which tracks cvs commits can be used to
> track commits to the driver packages, and shoot off an email to the
> "testers" that a new version is in CVS. It'd be fairly easy to do,
> actually. I could throw something together (emails would come from my
> gmail though probably) pretty quickly if I'm thinking this through
Roman Kyrylych (Роман Кирилич)
More information about the arch-dev-public