Hi,
Am 23.04.2012 um 08:36 schrieb Carsten Ziegeler:
> Hi,
>
> hmm, I'm wondering what our plan here is :) I know that we talked
> about it long time ago, recently Bertrand tried to use some new
> mechanism which would allow us to keep Confluence. I really have no
> real preference but would like to keep to amount of work in this area
> as low as possible.
Confluence export and rsync will be disabled by the end of the year.
There would be a a mechanism (IIRC Camel uses it) to regularly poll for updates
and convert them in to svnpubsub stuff. This polling and conversion is IMHO
brittle and prone for failure.
I think migrating to Apache CMS has a number of advantages:
* We are in line with the ASF infra strategy (read "good citizenship")
* The conversion is a one-shot job
* Editing is as easy with CMS as with Confluence (IMHO once you get
used to markup)
* Less things to be maintained by us (nothing in fact)
* Possibility to propose updates as patches through JIRA
* The only thing we would have to change is, that only committers
are allowed to update. So we would have to invite some docu
people as committers (not a big deal for me).
I think we should keep the Sling Wiki in Confluence, though.
Regards
Felix
>
> Regards
> Carsten
>
> 2012/4/22 Felix Meschberger <[email protected]>:
>> Hi all,
>>
>> I am currently taking another stab at converting our Confluence site to use
>> the new ASF CMS.
>>
>> So, expect lots of commit messages while the site is being built for the
>> staging site. You can look at it (currently rather horrible ...) at
>> http://sling.staging.apache.org
>>
>> Regards
>> Felix
>
>
>
> --
> Carsten Ziegeler
> [email protected]
