Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 89046 invoked from network); 18 Jan 2005 16:32:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 18 Jan 2005 16:32:04 -0000 Received: (qmail 97142 invoked by uid 500); 18 Jan 2005 16:31:56 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 97089 invoked by uid 500); 18 Jan 2005 16:31:55 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 97072 invoked by uid 99); 18 Jan 2005 16:31:55 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from viefep18-int.chello.at (HELO viefep18-int.chello.at) (213.46.255.21) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 18 Jan 2005 08:31:55 -0800 Received: from [192.168.1.31] (really [62.178.239.20]) by viefep18-int.chello.at (InterMail vM.6.01.03.04 201-2131-111-106-20040729) with ESMTP id <20050118163150.ZGMU20143.viefep18-int.chello.at@[192.168.1.31]> for ; Tue, 18 Jan 2005 17:31:50 +0100 Message-ID: <41ED39F0.9060104@apache.org> Date: Tue, 18 Jan 2005 17:31:44 +0100 From: Reinhard Poetz User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [proposal] Cocoon documentation system References: <41E772B7.8010207@apache.org> <6E0707BF-6606-11D9-B7AF-000A95AF004E@apache.org> <41E82E41.6010701@apache.org> <20050115005102.GA10528@igg.indexgeo.com.au> <41E88852.9010204@apache.org> <41E8DBF1.20900@apache.org> <41E96E9F.6000508@apache.org> <41EB981F.5020404@apache.org> <41EC1544.9000003@apache.org> <41ECC0BC.4000101@apache.org> <019101c4fd38$7b77ef30$a501a8c0@computer2> <41ECCFFA.7@apache.org> <3A45BDC2-6934-11D9-87E0-000A958B684A@outerthought.org> <41ECDE1B.90503@apache.org> <41ECE9D4.5000303@apache.org> <41ECFF27.2050300@apache.org> <41ED26BF.9010308@apache.org> <41ED3514.2080102@apache.org> In-Reply-To: <41ED3514.2080102@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Torsten Curdt wrote: >> every new/modified doc has to be approved by a committer. My plan is, >> that this approval is part of the online webapp. > > > >RT> > > Why not simple moderation via email? > > Committers could subscribe to a special closed mailing > list. The webapp send emails with diffs and a link with > a token. If anyone clicks on the link the webapp will > commit the change. > > Well, or you could even count the clicks and require > e.g. 3 committers to acknowledge the change > > ...things like that. > > Due to the amount of committers we would have > still quite a good response time until changes > appear live. ...which is important IMHO. > > > > Though I doubt the infrastructure folks > would like to give a webapp commit privileges. > > Actually it would also be even nice to pass on the > credentials of the clicking/committing committer. > > So using a ssh to execute a remote command would > be another option... > > The point to success: it must be comfortable - for > users and committers. > > My 2 cents Thank you. But as you say, it depends if it is allowed that either a webapp or a mail server is allowed to do a commit. If yes, we have many options. If no, having a locally running application that does the actual commit could be a workaround and I think rather comfortable for committers. -- Reinhard