Yuval Kashtan <email@example.com> writes:
> 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.
There is that advantage, yes. But there are also considerable
disadvantages: deciding exactly what abilities should be added to
mod_authz_svn would require a long and complicated discussion here
(obviously we can't just take your particular requirements as the
guide, we have to think about the whole question from the ground up).
It might also involve compatibility issues with previous versions of
mod_authz_svn and/or mod_dav_svn.
I personally don't find the requirement compelling. Since this is
version control, people can as easily review events after they happen
as before -- it can always be reverted, after all. This is not to say
that you don't have good reasons. But implementing it in a pre-commit
hook means you don't have to get the rest of the Subversion dev team
excited about the feature. Implementing it in mod_authz_svn means you
do, which might be difficult. My suggestion is to use a pre-commit
hook. That has its own kind of simplicity, though I understand your
desire for another kind of simplicity...
> On 03 Dec 2004 15:04:33 -0600, firstname.lastname@example.org <email@example.com> wrote:
> > Yuval Kashtan <firstname.lastname@example.org> 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: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sat Dec 4 19:10:03 2004