[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: rev 3010 - trunk/notes

From: Justin Erenkrantz <jerenkrantz_at_apache.org>
Date: 2002-08-22 23:47:53 CEST

On Thu, Aug 22, 2002 at 11:33:46AM -0700, Greg Stein wrote:
> And note that (IMO) any ACL support should begin with WebDAV ACL support in
> Apache itself.

My impression based on the WebDAV ACL spec was that enforcement is
based on properties. Therefore, a mod_dav wouldn't *need* to be
involved. But, I do need to read up on the WebDAV ACL draft and
then look at mod_dav and see what would have to change there.

And, partly, in order to add WebDAV ACL support to mod_dav, it needs
something that uses ACLs to provide impetus. I volunteer Subversion.

> > If a clean, simple design emerges well before 1.0, perhaps it can even
> > get into 1.0.
> Let's stress "clean" and "simple" :-).

Unlikely for 1.0, but I don't think that the collective 1.0 effort
will be impacted much if I go off and see what it would take and
perhaps start a coding effort. It's not like I'm that important.
(Which is why I don't mind if the CollabNet group doesn't pay much
attention to this now.)

> [ I'm hoping most SVN developers here agree that getting 1.0 out now is a
> higher priority than more features ]

It's 1.0 for me as I'm using it.

As I said before, I needed a mechanism for WC permissions. I've
already coded it up and it works, but obviously, no one is interested
in seeing that in SVN itself. *sigh* I think you're missing a
feature that people *might* want (it's opt-in).

But, I'm content to start trying to tackle the WebDAV ACL. At least
that way, I can start to potentially refine what would make the WC
permissions better. Hopefully, that'll please Bill. -- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 22 23:48:27 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.