On 11/9/06, easyproglife <[EMAIL PROTECTED]> wrote:
Hi all. I am watching the "future of ivy" discussion and see many important notes. I think these blessed discussions are because of the move to Apache. In the Jayasoft forum, there was much less discussion but more things like technical help.
A big problem with Ivy forums was that weren't even a developer dedicated forum. The Apache effect is also important, I think it eases people to feel that they can get involved without giving their work to a private company. This is great for the future of Ivy! To help us all track the discussion, I want to try organizing the issues. Yes, the first discussion about Ivy future was too large with too many issues, not easy to follow. Do you guys agree to open a few smaller threads and try focus on specific
issues, instead of enhancing "the future of ivy" thread more and more? I think it would help us all concentrate and contribute ideas.
Xavier, do you see what are the main issues discussed here in the last few
days? Can you try open a separate thread to discuss any separate issue and make it easier to track the discussion?
I think it's almost going on like that now. The three main topics I see in the first thread are: 1- what could be done in a 2.0 version and how should we do it (with some subtopics like collaboration with maven team on metadata) 2- what should be the first version released in ASF, with which content 3- a discussion about metadata stability 3 now has its own thread (with some mails still in the first thread) 1 and 2 are still a little confused, I will start a new thread dedicated to 2 (on which steve and I have already agree) I think it would also be good to summarize the conclusions (if we have
some). Is a Wiki still an option?
I think a wiki would be a good option, and a good tool to work on Ivy 2.0. Maybe a Mentor could see if we can set up a confluence for Ivy (or tell me what I can do for that)? Xavier Thanks,
easyproglife.
