Hi 2010/5/21 Ulrich Stärk <[email protected]>
> 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. > In my humble opinion, documentation remains a key point and moving from confluence to cq5 shouldn't stop what has been initiated by you with confluence. As you said too many projects are using confluence as a CMS, also i guess it has an XML export feature or something like this that will leverage the migration process. I don't know cq5 but if it's a good tool it should have an import feature as well. Also, i think that most of the work with the documentation is to re-structure, fix and complete the existing one built with Maven. This is why i would like to see for 5.2 an appealing front page for Tapestry 5 that provides efficient link to documentation (confluence or maven at least) and important contributions, third party libraries... As an exemple, we have the component reference that is an efficient Javadoc like tool, but it is not enough emphasized by the actual design, existing first page contains to much information and the existing content is not accessible enough for newcomers. Sorry to focus again on documentation but the first step has been made with Confluence, and the discussion has been so long that we should'nt stop now or even stand by. What about the new hot reloading feature, at that time it is designed for development purpose, but it would be so great to make it available programmatically for production environment. I know this is a complex thing to achieve, but for maintenance and monitoring of applications it would be nice to have for exemple the ability of doing a full registry restart and make the application off for a period of time (system administrator's dream :) I don't think we are so far from it. Maybe for a 5.3. Regards, Christophe Cordenier. > > Uli > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Regards, Christophe Cordenier. Developer of wooki @wookicentral.com
