Hi Oh been too busy with work, than having the time to read this thread and respond.
On Wed, Jan 16, 2013 at 10:12 PM, Christian Müller <christian.muel...@gmail.com> wrote: > I find it very difficult to start a such huge and important challenge as > Camel 3.0 will be, for sure. I think the most difficult part is to get > consensus about what we do it and how we do it. We already collect some > useful ideas at [1], but I have the feeling we have to review these ideas. > First of all, because I don't think we can do all of them in one release (I > also have a few more - more important from my point of view - ideas, > collected from users, contributors, committers and PMC members). Second, > some ideas need more "meat" before someone else than the authors know what > this means and which impact it has. Third, a few of these ideas are already > implemented in Camel 2.11 or before, so that we can remove it from this > page to be more focused. > > - Rename "Camel 3.0 - Roadmap" into "Camel 3.0 - Ideas" > Yeah good idea to rename it to "ideas" as that page was frankly just ideas we have noted down over the time for possible inclusion in Camel 3.x. > - Start a fresh "Camel 3.0 - Roadmap" WIKI page which we will fill with > content in the next weeks > - I propose to subdivide this page into three (child) pages: > - What has to be done before we can start working on Camel 3.0 (probably > during the (short term) Camel 2.12) > - What are the changes we do in Camel 3.0 > - What is postpone to 3.1 or later > - Afterwards we put everything together, we will see on which ideas we > already agree and which ones requires detailed discussions. Yeah having a new 3.0 roadmap page is a good idea. And another page for ideas for the future. Though I suggest to not tie that into 3.1 etc. Just for the future eg in the 3.x timeframe. > - For later ones I propose a weekly (or two times per week) IRC/Skype > session for discussion (Which days/time fit best for you?) > - We should also start a [DISCUSS CAMEL-3.0: <TOPIC>] thread at dev@ for > the guys they are not able to attend > - Afterwards we will send the results to the dev@ mailing list to share > it (if you are interested in it, join us at dev@camel.apache.org) > Discussions *should* happen on the @dev mailing list, so everybody can be in the loop and participate. Its the Apache way. > I will start with it after 72 h to give everyone the possibility to suggest > another approach (I will only start writing down some ideas which are not > on table right now). And of course, every help is welcome. A simple -1 or > better +1 ;-) is not much, but also helpful and better than no feedback... > Better, if you join us [2] and ride together with us Camel 3.0. > Frankly with the work load and what else people do in their daily job, they may not have the time to give their feedback and thoughts about this if the timeframe is as low as 72 hours. I barely had the time to do so. Though as I guess no final decisions is made within this time. I see no issue wit starting the work with the wiki pages. That should be ongoing for some time, so all have had the amble time to give their feedback. > [1] http://camel.apache.org/camel-30-roadmap.html > [2] http://camel.apache.org/contributing.html > > Best, > Christian > > -- -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
