Re: [Monotone-devel] Re: ikiwiki and monotone

[Daniel Carosone]

On Fri, Oct 13, 2006 at 10:38:06AM +1000, Brian May wrote:
> >>>>> "Daniel" == Daniel Carosone <address@hidden> writes:
> 
>     Daniel> Consider a 'moderated' page flag: rather than blocking out
>     Daniel> web edits of 'important' pages entirely as some wiki's do,
>     Daniel> allow web users to submit edits as extra heads (into a
>     Daniel> review branch?) and then have admins approve/merge them
>     Daniel> back to the public content later.
> 
> Alternative suggestion: a moderation certificate. 

Sure, it's the same thing with a different certificate name.

> Revision must be signed by X, Y or Z before shown on the
> wiki. Alternatively, must be signed by X Y and Z. Would this work?

Sure. The X/Y/Z requirement amounts to setting the update trust hooks
for the build workspace when recompiling the pages.

You don't need to use separate branches or separate certs at all.
Doing so just and borrows convenience from the existing use of branch
assertions to represent fitness-for-purpose.  You could require
testresult certs for tests like valid markup syntax and referential
integrity between pages if you liked, too.

You either implement this logic in the trust hooks directly, or
indirectly, which would amount to your moderation cert - see the
TrustBot pattern on the monotone wiki.

Either way, add some simple UI to tell the user "your submission has
been accepted for review and approval" so they don't get confused, and
perhaps links to search viewmtn for other edits pending approval.

The thing is that certs are whole-revision, whatever cert you use.  In
the sample scenario, you want to allow arbitrary web submissions to
most pages, but moderate some. So you need a way to flag these pages
for special handling. This could be an attr, or maybe a PageSpec. 

Then one of two things happens:
 - web commits for pages with this flag tell the cgi to commit to the
   for-review branch, while others go to the main branch
 - all web commits go to the review branch, and the TrustBot then auto
   merges/approves revs on that branch that *don't* involve a file with
   this attr, leaving the others to be merged by people.

They're pretty similar, one just puts the bot within the cgi and
closer to the wiki, the other works with netsync submissions too.

--
Dan.

pgpWz8Ul_kk2_.pgp
Description: PGP signature