Given that the individual backends are independent and change a lot
faster (or should, anyway) than the SANE core, this makes sense to
me. It would take a lot of the load off David if he didn't have to
assemble patches for various backends (or other sub-projects) himself.
I'm not convinced that it's a good idea to give all maintainers the
ability to create whole releases though. Perhaps having a couple of
people with that authority would be sufficient to avoid the bottleneck
problem? Is there a way to give maintainers restricted write access,
say to just the part of the package they are responsible for?
-- Kevin Charter firstname.lastname@example.org | email@example.com http://www.cs.rice.edu/~charter | http://www.cs.ualberta.ca/~charter
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail firstname.lastname@example.org