Am not sure, of course, but I think the authz is a better place to put
this as it will keep authorizations as a single, whole, solution.
On 03 Dec 2004 15:04:33 -0600, kfogel@collab.net <kfogel@collab.net> wrote:
> Yuval Kashtan <yuvalkashtan@gmail.com> writes:
>
>
> > Hello to all the folks @ subversion dev,
> > there is a suggestion I want to discuss with you:
> >
> > Currently, SVN support only Read/Write (and none) authorization roles.
> >
> > I find it highly usefull to restrict also who can add/delete files.
> > Adding / Removing of files have alot to do with the project
> > configuration managment.
> > In a big project I want such changes to be more carefuly considered
> > and controlled (for example, allowing only team leaders to add files
> > only after they read through the code and approved it and letting only
> > the project manager to delete / remove files so he can better control
> > what is going out).
> >
> > It seems that such a change can be pretty easially achieved, as it's
> > involves only changes to mod_authz_svn.c
> >
> > What do you think?
>
> Are you sure you need to modify mod_authz_svn.c to do this? You could
> implement it in a pre-commit hook too.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Dec 4 18:52:25 2004