Hi Vik > Maybe we should organise a web conference to get a little focus on this? > + 1 Thanks for providing the conference server. When shall we meet ? The evening after 19:00 UTC+1 (MEZ) would be fine for me.
Rudolf > The conference server from the Lenya meeting is still available for us > to use. > > I am headed to the woods in a couple of hours > Watch out wildlife! :) > > > Regards > > > Vik > > On 11/05/2010 06:03 PM, florent andré wrote: > > Hi Richard, thanks for this feedback. > > > > In the same wave, I read the paper on ASF CMS [1] and particularly the > > part on Lenya ! > > > > I can't stop myself to ask more details from them !:) Hope they give > > useful points for us. > > > > You can follow the thread here (mail just send, not now in the archive) > > : > > http://mail-archives.apache.org/mod_mbox/www-infrastructure-dev/ > 201011.mbox/browser > > > > > > Title of the mail : Fondation cms and Lenya > > > > ++ > > > > > > [1] http://www.staging.apache.org/dev/cms.html#lenya > > > > On 11/05/2010 01:46 PM, Richard Frovarp wrote: > > > >> I presented at ApacheCon yesterday and it went well. I did get some > >> questions from audience members that can help guide us as we work on new > >> features. Replication was one thing I was asked about and going forward > >> it would probably be a very good thing to support. > >> > >> I would like to see us move forward on the v3 design. At Bordeaux > >> Andreas drew up a possible architecture, and the general consensus at > >> that meeting is that feature requirements should come before choosing > >> any technology to implement. Florent has done some overview for us since > >> then as far as features and/or architecture. > >> > >> I am headed to the woods in a couple of hours and will be without > >> internet over the weekend. However, I will try to work on an existing > >> feature list and come up with a list of possible features we'd like to > >> add. I'll also attempt to classify the features in a couple of ways so > >> that they can drive the architecture and some of the actual development. > >> > > --------------------------------------------------------------------- > > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
