> [Oliver Rauch]
> > I disagree here!
>
> Being able to change the whole source does not mean it is permitted.
>
> I expect everyone with write access to the source understands this
> difference, and accept that only the backend maintainer make changes
> to his backend.
>
> > Normally there is one person who works on a backend. It is not a
> > good idea if anyone has write-access to the backends. If someone
> > else wants to change anything on a backend, he should mail his patch
> > to the author of the backend.
>
> Exactly. You don't need to block write access using CVS to make this
> happend. There only has to be agreement between the people with write
> access.
>
> [Kevin Charter]
> > Is there a way to give maintainers restricted write access,
> > say to just the part of the package they are responsible for?
>
> [Oliver Rauch]
> > If we use CVS, that is the only way that makes sense!
>
> Why use technical means when all that is needed is general consencus?
Ok, that would be possible - although I understood the original message that
EVERYONE
should get write access. But I think CVS should be able to set permissions for
each file
and that would be the best solution!
Bye
Oliver
-- 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 majordomo@mostang.com