> > Is there a way to give maintainers restricted write access, say to
> > just the part of the package they are responsible for?
> It is smarter and easier to let social control take care of this too.
> If there is disagreement on some change, it can always be reversed
> using CVS.
> When a summary of all changes to the current source in addition are
> mailed to all maintainers, it is easy to keep track of the changes.
I disagree here!
Normally there is one person who works on a backend.
It is not a good idea if anyone has write-access to
If someone else wants to change anything on a backend,
he should mail his patch to the author of the backend.
In most cases only the backend author is familiar enough
with the backend, so he has to check a patch at first before
it gets into the offical source!
I think it could be good if the backend authors would
update their part in CVS!
But in fact there is no great advantage because a user needs
a recent sane version and has to update the backend he
uses, so there is not much more work than getting the CVS version!
-- EMAIL: Oliver.Rauch@Wolfsburg.DE WWW: http://www.wolfsburg.de/~rauch
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail firstname.lastname@example.org