Jeremy wrote: > It's very easy for committers to make changes using CMS, but for > contributors (inlcuding those who don't have an ASF id) they have to > check out the site, configure the build env, build it (instructions on > our site) and submit a patch. Then the committer applying the patch > also needs the full site checked out and configured to build. I think > that process could be improved on, but that would need changes in CMS > a) to allow anyone to make changes in a sandbox and create a patch for > a committer b) for a committer to be able to take that patch and apply > it. > > So I don't think the patch process doesn't work (unless you can > elaborate), just that it's long winded.
Patching documentation is not something I have direct experience of myself, so I should avoid getting myself in too deep into this discussion! I was judging by Alasdair and Charles's comments at the end of https://issues.apache.org/jira/browse/aries-597, and so Alasdair or Charles is probably better placed to comment than me. It appears Alasdair tried several times to merge in Charles's patch, sent it back to Charles to see if Charles could do anything, and then ended up manually merging in Charles's changes, with the comment "I guess the diff capability in Apache CMS is broken, or not intended for creating patches. " If we have to do that every time it won't be a great experience for either committer or patch-provider. But maybe there's a better way. Holly Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
