diff options
author | joey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071> | 2007-08-08 04:04:46 +0000 |
---|---|---|
committer | joey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071> | 2007-08-08 04:04:46 +0000 |
commit | 423f4aedbdce45ee995bab8dc94b88ad68890981 (patch) | |
tree | fb903cc4cb0c9959c3e4b63b478036da1ab874d4 /doc | |
parent | 44d6fa4db19af2a1562f318dece16d9e6decbc9b (diff) |
web commit by http://jeremie.koenig.myopenid.com/
Diffstat (limited to 'doc')
-rw-r--r-- | doc/todo/review_mechanism.mdwn | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/todo/review_mechanism.mdwn b/doc/todo/review_mechanism.mdwn new file mode 100644 index 000000000..13fc248e2 --- /dev/null +++ b/doc/todo/review_mechanism.mdwn @@ -0,0 +1,20 @@ +Basically, what I need is a two-sided wiki: + +* one side would be the published version, with the ikiwiki CGI disabled; +* another would be the developement version, which would be editable online. + +These two sides would correspond to branches in the repository. +Each time someone makes a change to the developement version, +the created revision number would be added to a list of changes to be reviewed, +maybe by a pre/post-commit hook. This would be done only if a published version of +the page exists, and could be requested when a new page needs to be published. +Some kind of priviledged user could then move the change around, +from the "review needed" queue to the "accepted" or "rejected" ones. +This would be done in a way that would trigger the appropriate VCS merge operations. + +A generic "change queue" mechanism could be used for translations or other stuff as well. +Each change would have its own wiki page under changes/revNNNN. +Change queues would be wiki pages as well (probably using [[inlines|plugins/inline]]); +[[Pagespecs|Pagespec]] and [[tags]] would be used to control the queues to which a given change would belong. + +--[[JeremieKoenig]]
\ No newline at end of file |