From rlpowell@digitalkingdom.org Thu Oct 10 11:14:20 2002 Received: with ECARTIS (v1.0.0; list lojban-list); Thu, 10 Oct 2002 11:14:20 -0700 (PDT) Received: from rlpowell by digitalkingdom.org with local (Exim 4.05) id 17zhpB-0001Ya-00 for lojban-list@lojban.org; Thu, 10 Oct 2002 11:14:17 -0700 Date: Thu, 10 Oct 2002 11:14:17 -0700 To: lojban-list@lojban.org Subject: [lojban] Re: Final Translation Wiki Idea: PLEASE READ. Message-ID: <20021010181417.GD1332@digitalkingdom.org> Mail-Followup-To: lojban-list@lojban.org References: <5.1.0.14.0.20021009205420.02e4bd80@pop.east.cox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i From: Robin Lee Powell X-archive-position: 2116 X-ecartis-version: Ecartis v1.0.0 Sender: lojban-list-bounce@lojban.org Errors-to: lojban-list-bounce@lojban.org X-original-sender: rlpowell@digitalkingdom.org Precedence: bulk Reply-to: lojban-list@lojban.org X-list: lojban-list On Thu, Oct 10, 2002 at 09:52:17AM -0700, Jim Carter wrote: > On Wed, 9 Oct 2002, Nora LeChevalier wrote: > > I wish to suggest relying on the goodwill of all involved instead of > > only automatic locking. If, as a custom, one who wishes to log out > > a piece of work would put a (dated/timed?) comment to that effect at > > the top, to be removed when the final posting is done, others who > > are willing to abide by the convention will not make changes despite > > the page not being locked. The duration of the lock may then become > > a non-issue. > > By coincidence, just yesterday I sent around a message in my work > group chiding people for forgetting to remove equivalent > expiration-dated notices. Heh heh. > I wonder if the lock time could be configurable at the time of > checkout, according to the particular person's style of work -- which > apparently varies widely. Not without writing code. > Can locks be renewed, if the modifications go more slowly than > expected? Yes; you can save your edits and re-edit. 8) > Good fences make good neighbors. Automated locking on the server can > cheaply give a lot of help in coordination. Locking (one lock per > file) is standard practice in software development. -Robin -- http://www.digitalkingdom.org/~rlpowell/ http://www.lojban.org/ la lojban. jai curmi roda .einai to ku'i so'ada mukti le nu co'a darlu le'o -- RLP I'm a *male* Robin.