On 10 November 2010 14:51, Daniel Kulp <dk...@apache.org> wrote: > On Wednesday 10 November 2010 9:43:13 am Guillaume Nodet wrote: >> On Wed, Nov 10, 2010 at 14:40, Hadrian Zbarcea <hzbar...@gmail.com> wrote: >> > Thanks James, >> > >> > You have to comment out the dependency on scalate-test in the pom for >> > this to work (otherwise you get a "Failed to resolve artifact"). >> > >> > That aside, one of the important requirements I believe is not to raise >> > the barrier to entry for those who want to contribute documentation. >> > Today, one only needs to have a icla signed at apache and edit the wiki >> > in place. >> >> This can be done by submitting a patch attached to Jira. > > Which is still a fairly high barrier. > > For CXF, we recently got a volunteer > that has been doing a WONDERFUL job cleaning up various pages on the website. > That individual has dived right in and started working on thing. > He's also > logged some JIRA issues about updating javadoc and warnings and such, but I'm > having problems working with him to get patches created. For some people, > working with something like svn or git or even maven is a challenge. It is > more stuff to install (everyone has a browser installed) and learn. > > For most of the people on this list, it ISN'T a big deal. We deal with svn > and mvn every day. For others, it could be.
Given 99% of all our documentation and web content is developed by committers or folks who are capable of editing text files and using git/svn, I'd rather use a system that helps the 99% be more effective. Maybe you should just help out this one CXF person & show them how to fork & commit to github (its very easy), then you can easily pull their commits from there? -- James ------- FuseSource Email: ja...@fusesource.com Web: http://fusesource.com Twitter: jstrachan Blog: http://macstrac.blogspot.com/ Open Source Integration
