On Fri, 11 Mar 2005 15:58:22 +0000 Ciaran McCreesh wrote: > On Fri, 11 Mar 2005 15:50:01 +0000 Ian Leitch > wrote: > | I propose that a dev is free to upload a GLEP in any state of > | completeness/correctness as they wish, devs can then vote on said > | GLEP. If the GLEP author makes changes, devs then vote again on that > | revision. This system also gives power back to the devs (and users > | if they're allowed to vote) and away from the GLEP editors. > > 'Any' state is asking for trouble. You can post non-finished GLEP > plans to the list in any state, but I'd expect things making it onto > the site to be at least in reasonable draft state. Agreed, but being able to have potential/unfinished gleps available (so you can check them by url, but not by clicking a link on the index) would be nice so people who are asked by glep authors to proofread/comment/poop on a new glep don't have to remember all the custom d.g.o URLs. Another thing is that I'd like to update it directly and not to have to send diffs/new versions to some gatekeeper instance. So maybe direct commit access for devs (as mentioned in GLEP1) with some special magic for the index page? Marius -- Public Key at http://www.genone.de/info/gpg-key.pub In the beginning, there was nothing. And God said, 'Let there be Light.' And there was still nothing, but you could see a bit better.