> -----Original Message----- > From: Steve Loughran [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 08, 2006 12:37 PM > To: [email protected] > Subject: Re: future Ivy development >
> > I'd probably put priority on getting the first edition under > the apache > banner out the way; build process, testing, documentation and > the like. > A goal of a 2.0 release would be to get more developers than > just Xavier. > > -steve > > I think you get a good point there. The question is : what is the best aproach to achieve that? >From my point of view, I already had the oportunity to look in the sources, and I tried to made some changes to it. But I only managed to post 1 or 2 patch because I was not sure to break any flow of execution. The problem is that there is so many way to use ivy. Much more that what I'm aware of. (on the other hand, it is also for this reason that I like ivy). I like the idea of easyproglife to start by listing some use cases. I think this can be a good starting point to clarify the different possible usage. Rewrite (or refactor) a 2.0 version would also make it easier for new developpers to join. On the other hand, a 2.0 would not have any users before a while. And without users, is there a community? So if ivy goes for a 2.0 version, what should be done is to encourage the 1.x user community to express their requirements and their needs. But I fear it's difficult to achieve. Gilles PS: By the way, Python community has good example of process to manage enhancements. (see http://www.python.org/dev/peps/) I don't know excactly how it works. But I like the idea, even if it might be too heavy for the ivy community.
