I wouldn't worry too much about possible migration away from Confluence. What you've put together works well now and if Tapestry needs to move to another system in a year so be it. I've read the same, but it's more than likely that it'll take longer or just won't happen (just read the discussions about moving away from the KEYS infra, started in 2007 or earlier...) and I doubt the Atlassian crowd (no pun intended) will stay still in the meantime. Confluence wiki is better for the intended purposes than what's in place right now and you've already done all the work for it. CQ5 path is uncertain at the moment - what if the final decision goes against deploying it?
Kalle On Fri, May 21, 2010 at 1:42 AM, Ulrich Stärk <[email protected]> wrote: > On 20.05.2010 04:19, Howard Lewis Ship wrote: >> >> I'd be interested to hear what the other developers see as must-haves >> for a 5.2. I know I'd like to see what's going on with the new >> Confluence documentation. > > Confluence documentation seems to work like a charm. For starters I migrated > the cookbook to confluence. There is one thing we should consider though. > The ASF is planning to move away from confluence being abused as a CMS and > will install a full CMS in the very near future. They'll start experimenting > with Day's CQ5 in the next few weeks and want to discontinue Confluence as a > CMS by the end of the year (though I doubt that they actually will because > too many projects are using it that way and all the content will have to be > migrated). > I've offered infrastructure to be a pilot tester and will help evaluate the > new CMS and see if it would fit for us. There is no sense in migrating to > Confluence now when it will be discontinued in a year or something but that > needs further discussion. > > Uli > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
