Ok. I will continue to provide patches. I will work on pages about Blueprint to demystify that and explain in more detail options of Aries JPA and Aries Transaction.
On Fri, Mar 25, 2011 at 12:47 PM, zoe slattery <[email protected]> wrote: > On 25/03/2011 11:33, Charles Moulliard wrote: >> >> Which decision has been taken finally to allow to provide >> content/documentation and commit it into Aries project ? > > No decision afaik. > > Might I suggest that you continue to submit patches? That will at some stage > force a > discussion on commit rights. I think what you are doing is extremely > valuable. > > Zoe >> >> On Fri, Mar 18, 2011 at 5:51 PM, Guillaume Nodet<[email protected]> wrote: >>> >>> What does the CMS bring to scalate ? Maybe I'm missing something, but >>> I don't really see the value of a webapp that simply do the commit on >>> your behalf. Though I haven't used it a lot, so I'm sure I'm missing >>> a lot of nice features here. >>> Using pure scalate, you can have a live editing view of the website >>> using scalate by running mvn:jetty -Plive in Karaf for example. If >>> you use chrome, you can even plug in livereload so that the pages are >>> updated automatically. When you want the changes to go live, you can >>> mvn scalate:deploy, and that's all. >>> >>> >>> On Fri, Mar 18, 2011 at 17:23, Daniel Kulp<[email protected]> wrote: >>>> >>>> On Friday 18 March 2011 10:05:54 AM zoe slattery wrote: >>>>> >>>>> On 18/03/2011 13:44, Charles Moulliard wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> My question is perhaps stupid but why don't we use wiki/confluence >>>>>> like Apache ServiceMix/Camel/Karaf/ActiveMq projects. I know that >>>>>> confluence is not the most powerful tool to be used but it helps a >>>>>> lot. Additionialy, we use maven plugin to generate Camel manual. This >>>>>> process has been enhanced with Apache Karaf project using >>>>>> scala/scalate to generate the manual in PDF, HTML format. In this >>>>>> case, the pages of the manual are edited manually (outside of the web >>>>>> site) and this process is governed by SVN >>>>> >>>>> See here: http://www.apache.org/dev/cms.html >>>>> >>>>> The short summary is that confluence will not be supported and any >>>>> projects using it should be moving to CMS which is actually a lot >>>>> bettter :-) >>>> >>>> "A lot better" is certainly subjective. I wouldn't agree with it. :-) >>>> The markdown syntax of the CMS certainly is a step backwords compared to >>>> the >>>> Confluence syntax. >>>> >>>> What I kind of keep hoping for is that one of the Scalate experts would >>>> step >>>> up and wire Scalate into the CMS (write an extension mapper thing for >>>> the cms) >>>> that would allow using Scalate with the CMS. Thus, we could retain the >>>> use >>>> of the Confluence syntax (Scalate has a templating thing for that), but >>>> still >>>> be able to use the CMS. >>>> >>>> >>>> Dan >>>> >>>> >>>>>> Regards, >>>>>> >>>>>> Charles >>>>>> >>>>>> On Fri, Mar 18, 2011 at 2:04 PM, Holly Cummins<[email protected]> >>>> >>>> wrote: >>>>>>> >>>>>>> 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 >>>> >>>> -- >>>> Daniel Kulp >>>> [email protected] >>>> http://dankulp.com/blog >>>> Talend - http://www.talend.com >>>> >>> >>> >>> -- >>> Cheers, >>> Guillaume Nodet >>> ------------------------ >>> Blog: http://gnodet.blogspot.com/ >>> ------------------------ >>> Open Source SOA >>> http://fusesource.com >>> > >
