On Tue, 03 May 2011 09:58 -0700, "Michael MacFadden" <[email protected]> wrote: > All, > > We have been making steady progress on the infrastructure migration. The > next steps in my mind are: > > > SVN Migration > > This is pretty self explanatory, but we need to start thinking about how > and when we want to do this. > > > Code Reviews > > Once we move to SVN we can start using https://reviews.apache.org for our > code reviews. > > > Web Site / Developer Wiki > > This is a little more tricky. We were pretty spoiled over at > waveprotocol.org in terms of the google site's wiki interface. It seems > like the Apache CMS is not a polished in terms of managing a dynamic > site.
Remember, that the CMS is a thin layer over SVN. So for import purposes, you're best off just building a site locally then committing the thing wholesale - i.e. don't use the CMS to make your initial site. > We have lots of content that needs to be migrated over. I am not > 100% certain we want to try to force all of this in to the apache CMS. Don't know if the above statement changes that view. > We also have confluence which could be used for a developer wiki. We > could use the CMS for more static content and use confluence to house the > developer wiki. > > However, I am not certain as to the future of the confluence wiki at > Apache. More investigation on what our options are needs to happen. We > should look to see what other projects are doing and get some feedback > from them. The future of Confluence as a back end to web sites is short, its future as a Wiki is safe. Note, there's also MoinMoin wikis too. Upayavira
