[Monotone-devel] Re: Using monotone in a team

[Boris]

Oren Ben-Kiki wrote:
> [...]
>> I guess it does not belong to monotone. As you even want to forbid
>> developers to change trust policies I think a distributed revision
>> control system is not what you want. What monotone does is copying
>> data between databases. Once it is there revisions can be combined
>> flexibly. And how they are combined depends on the local
>> configuration (the hook functions). At least that's my understanding
>> so far (as usual without any warranties ;).
>
> Sounds strange to me. I'd expect the trust policy and (all? some?) of
> the hooks to be part of the data that monotone allows copying between
> the databases.

I can't comment on this. The answer probably depends on the motives why 
monotone was created and what kind of problems the original developers faced 
with other revision control systems. There is an introduction at 
http://venge.net/monotone/ and some information in the FAQ. However it is 
not clear to me what the key features are and what other features were 
simply developed to support the key features.

If I read for example the answer to "What is the networking protocol?" in 
the FAQ I'm not sure if netsync as it looks like today is a key feature of 
monotone. If it is then copying trust policies around does not belong to 
monotone. If it is not then monotone could be changed indeed. Is there any 
document which says what the explicit goals of monotone are?

Boris

> [...]