On Wednesday 15 December 2010 11:20:32 am Jeremy Hughes wrote: > On 15 December 2010 14:38, Daniel Kulp <[email protected]> wrote: > > Now that Zoe has everying working very well in the CMS, why not just use > > that? > > Seriously, it can be (might already be) setup so any Apache committer > > can edit and stage content (only an Aries committer can "publish") so > > you could edit away and avoid all the patch process and such. > > You're right, any committer can take a patch to the Aries website and apply > it. To use the patch command line they'd have to have the website checked > out locally rather than using the CMS web UI.
In confluence, we pretty much had it setup so that anyone with an ICLA filed could edit directly. We cannot really do that with the CMS, but we CAN make it that anyone with a committer account could. Basically, make the path to the site content open to committers: [incubator/aries/branches/site/trunk/] @committers = rw [incubator/aries] @aries = rw but leave: [/websites/production/aries] @aries = rw That would allow all committers to use the CMS web frontend (if they want to, it's kind of not the greatest frontend) (all committers need to have an ICLA so legally covered) to edit and commit changes directly. Buildbot would build it and stage it. But only an aries committer could do the final review and hit the "publish" button. I guess that's one nice thing about the new CMS in that the svn permissions can be used to control various things. BTW: that is how the main www.apache.org website is setup. @comitters can edit anything, but only @members/@pmc-chairs can publish it. Anyway, it's a thought. -- Daniel Kulp [email protected] http://dankulp.com/blog
