With a MoinMoin wiki we are still going to face the same kind of versioning
hell problems we have with our current wiki content.  We tend to use our
websites to document our products and that very quickly changes from
version to version.  Would be nice to be able to solve the versioning
problem by storing website doc in the same source branches as the products
so that they can stay in sync.

On Fri, Mar 23, 2012 at 3:01 PM, Jeremiah Jordan <
[email protected]> wrote:

> Why the need to make them static?  Why not move them to the MoinMoin wiki?
>
> http://wiki.apache.org
>
> ________________________________________
> From: [email protected] [[email protected]] on behalf of Hiram Chirino [
> [email protected]]
> Sent: Friday, March 23, 2012 8:55 AM
> To: ActiveMQ-Developers
> Subject: Need to migrate off Confluence Wiki
>
> ASF is going to take all Confluence instances offline I think by the end of
> the year.  We need to migrate our wiki docs to a static site generation
> tool.  The Karaf, Camel, and even Apollo project have or are migrating to
> Scalate based site generation system.  I guess we should follow suite and
> do the same.  Anybody interested in trying to tackle this big problem?  We
> would also need to do the same for thing the NMS and CMS sub-projects.  One
> of the side benefits to moving to a static site generation system is that
> we will be able to version our docs along with the project releases so that
> they stay in simple and in sync with project version.
>
> --
>
> **
>
> *Hiram Chirino*
>
> *Software Fellow | FuseSource Corp.*
>
> *[email protected] | fusesource.com*
>
> *skype: hiramchirino | twitter: @hiramchirino<
> http://twitter.com/hiramchirino>
> *
>
> *blog: Hiram Chirino's Bit Mojo <http://hiramchirino.com/blog/>*
>
> *
> *
>
> *
> *
>



-- 

**

*Hiram Chirino*

*Software Fellow | FuseSource Corp.*

*[email protected] | fusesource.com*

*skype: hiramchirino | twitter: @hiramchirino<http://twitter.com/hiramchirino>
*

*blog: Hiram Chirino's Bit Mojo <http://hiramchirino.com/blog/>*

*
*

*
*

Reply via email to