[Monotone-devel] Re: Best practice using monotone

[Bruce Stephens]

"Andy Jones" <address@hidden> writes:

> Okay, only one more dumb question that I can think of:  is there a doc
> somewhere that explains how the trust / quality assurance model works?

Just the manual, I think.

And I don't think anyone really believes what's there works
particularly well (in the sense of being what's actually wanted).
(Well, spot the lack of testsuite certs in nvm.)

There are some easy things that you can do: if you have a branch that
you want to regard as personal, then you can configure
get_revision_cert_trust to ignore branch certs not signed by you.
(Similarly if you want some branch to be signed by someone else.)

I think what's there was always intended to be replaced when someone
understood better how it ought to be done.

I believe the current thinking is to use special branches, and
these'll provide versioned policy, and all kinds of fancy things.
However, it all seems a bit vague to me.

<http://venge.net/monotone/wiki/VersionedPolicy> describes something,
but I suspect it's mostly orthogonal to what you're asking; it
concentrates on the versioning without mentioning too much on the
stuff that's being versioned.

[...]