Ivan Zhakov wrote:
> Hi,
>
> There are my ideas for SoC:
> * Store ACL in repository as special properties.
> It's very usefull feature. For example in our company project leads
> manages repository
> access. Now they need go to some Samba share for edit acl file.
>
Well, I store the mod_authz_svn config file in the repository, restrict
access to it, and arrange to automatically update changes to where the
server expects to see it. Project leads just use SVN to update access
rights, and it works just fine.
Storing ACLs in the repository is a BIG job, if it's done correctly (and
a -1 if it isn't ...). Definitely a lot bigger than C# bindings.
> * .NET (C#) bindings.
> I agree that it might too big for SoC, but initial level of bindings
> for libsvn_client will be good.
> There are some C# bindings around, but I consider Subversion should
> have "official" .net
> bindings.
>
So do you propose to duplicate AnkhSVN's work? AFAIK they have at least
complete client-side C# bindings for Subversion.
> * UI for shelves
> Shelves is storing local changes in some private branch on server.
> Many users asks for
> that. And most slighting that Subversion actually have it, but it
> hard to use:
> http://geekswithblogs.net/flanakin/archive/2005/12/02/61929.aspx
> http://blogs.vertigosoftware.com/teamsystem/archive/2006/01/18/Shelving_and_Branching.aspx
>
A "shelve" is a branch. So, instead of talking about a UI for shelves,
I'd recommend implementing some of the ideas that came up during the
discussion about using Subversion with the GCC repository.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 20 09:22:19 2006