On Tuesday 26 December 2006 00:36, Simo Leone wrote: > On Mon, Dec 25, 2006 at 04:09:24PM -0800, eliott wrote: > > I think the first logical step would be to figure out what works well > > in the current aur system, then set that as the initial functional spec > > for a rewrite. Work to duplicate current good features before adding > > more (yet make the system capable of adding additional features--ie. > > extensible). > > > > Then I think would be a good time to start adding additional features. > > Brainstorming these features now doesn't hurt, of course. I do think > > that trying to integrate current features, as well as new features, > > into a rewrite from the start will lead to a more convoluted > > and 'messy' end product. > > Well that's kind of where I was going with the wiki page... like you > know, the questions about what currently works and what doesn't? > > -S
The wiki idea should play well since we can focus on getting all the pros and cons in one place and really brainstorm on what improvements we can make. I will give the wiki a go, id love to be involved in the development process as well, I have been working with ajax intranet web-apps non-stop so I have some traction now lol. As a side note by my experience I have noticed that most system rewrites that I have worked on have been pain free when using some sort of Agile development methodology like Scrum since you focus on the basic pros of the current AUR and their improvements, extending them with some extra features. Cheers ^_^ -- Guillermo A. Amaral, BCSE @ site: http://www.guillermoamaral.com/ @ blog: http://blog.guillermoamaral.com/ # nick: thewonka / thewonka81
pgpOxySmbjuDy.pgp
Description: PGP signature
_______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
