bzr serve and access control?

Andrew Cowie andrew at operationaldynamics.com
Mon Feb 1 00:02:50 GMT 2010


On Sat, 2010-01-30 at 15:24 +0100, Josef Wolf wrote: 
> I have repositories that store how my
> network and computers are configured, which mail lists I am subscribed to,
> phone numbers and addresses of my friends and relatives, my financial and
> tax data, keys for my wlan.

Sure.

> I don't really think this data should be open-source.

Of course not.

The examples you gave are all personal & confidential information. The
question I have is why on earth these repositories and the data they
contain would be publicly visible at all? I'm sure you're just trying to
illustrate.

In any event, what you were asking for was finer grained user
permissions, but as Ben and I have suggested, there doesn't seem much
reason to mix proprietary commercial information and community visible
public information *in the same repository*. ie:

bzr://www.example.com/bzr/a-very-public-project/ and
bzr://www.example.com/bzr/super-secret-except-for-the-name/

are separate repositories containing project branch forests with
separate access controls - the former perhaps few to none [other than
managing committers, say] whereas the latter would have no public access
at all, enforced either by file system permissions or web server
configuration in the case of http://.

Somewhere along the way people seem to have got the idea that all work
needs to be in a single repository. [I can only think Apache's singleton
subversion server  is to blame, with *All* of the Apache Software
Foundation's projects having their code in a single svn repo. Talk about
a single point of failure]. On the other hand, having branches be
smaller than "project" size is also painful, because you have to come up
with some mechanism to combine these branches into a project.

AfC
Sydney


-- 
Andrew Frederick Cowie

Operational Dynamics is an operations and engineering consultancy
focusing on IT strategy, organizational architecture, systems
review, and effective procedures for change management: enabling
successful deployment of mission critical information technology in
enterprises, worldwide.

http://www.operationaldynamics.com/

Sydney   New York   Toronto   London






More information about the bazaar mailing list