I suggest doing a migration to svnpubsub first and switch to Markdown or whatever else we want to use for documentation generation later. It's the autoexport that's going away, not Confluence itself.
Also, we won't need any Django knowledge. The CMS' architecture might be influenced by Django but you certainly don't need to know anything about it in order to work with the CMS. Automatically generated source code documentation might indeed be a problem. We should find out how other projects are doing this. I don't like the idea of checking it back into SVN as part of the build process. Uli On 01.08.2012 21:15, Howard Lewis Ship wrote: > I think it's time that we switch over from Confluence to the CMS > > http://www.apache.org/dev/cms.html > > Looks like the CMS is going to be SVN regardless > > I'm hoping someone can volunteer to spearhead this; if not, I'll look > into it in a week or so. > > The docs kind of presume a lot of knowledge of some version of Django, > which I certainly don't have. > > I think markdown will be a fine format. I like that it will be > possible to navigate to a page and click an edit button. It should be > possible to open up our site repo to any Apache committer. > > I'm not quite sure what we'll do about published JavaDocs (and, > potentially, other reports, such as JavaScript/CoffeeScript docs). > Possibly, we'll need to generate those into an SVN folder and check > them into SVN for publishing to the site. > > I'm hoping the result will be something faster and easier to maintain, > and more customizable as well. > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
