>>>>> "Boris" == Boris <[EMAIL PROTECTED]> writes:
Boris> Question: There is no way (and I assume no need) to set
Boris> write-permissions per user? I don't see anything in the
Boris> documentation that I can use pattern and allow in
Boris> write-permissions, too?
I would assume you would need to do this, for each user, by overriding
the get_revision_cert_trust hook.
If multiple users have different projects with different policies,
this could get awkward.
I think there is a proposal to solve this issue, if I got to the bottom of
http://www.venge.net/monotone/wiki/TrustFoundations I see:
"Mechanisms to automate this, and allow delegation to a 'project
authority' for common VersionedPolicy statements that affect trust
evaluation are the next major development focus."
If I click on the link to
http://www.venge.net/monotone/wiki/VersionedPolicy though, I get lost.
Boris> Now junior developers work on their own branch while senior
Boris> developers can change code in the main branch
Boris> directly. From time to time a senior developer checks the
Boris> junior branch.
Boris> 1) Let's say everything is all right. He can then propagate
Boris> changes from the junior to the main branch and vice versa?
Boris> 2) Let's say the senior developer doesn't like the last
Boris> revision. Then he can disapprove it and revert it to the
Boris> previous revision? 3) Let's say he uses the approve
Boris> command which adds a certificate to the revision. How
Boris> exactly can this new certificate be used?
Boris> I especially wonder about option #3. Is there some
Boris> automatic support for approvals or is this something which
Boris> must be implemented in hook functions?
I believe the get_revision_cert_trust does this.
--
Brian May <[EMAIL PROTECTED]>
_______________________________________________
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel
