From: Walter C. <cha...@gm...> - 2006-03-28 16:19:26
|
Samuele, I agree with you that jython is complex simlar to a race car engine...alot of care is needed to prevent regression....maybe the gripes I have are that it doesn't "seem" to be moving quickly "enough" If it is a resoucing, talent issue...than it should be made known clearly where and what is needed...so we can use the strength of the community...the stakeholders to come to a solution. Just saying "no money" or "I'm only doing it in my spare time" is not healthy for a project with such great potential.... If prioritzation is problematic, perhaps the bug tracking system the sf has isn't doing it for us....or if that's not the case...what is?? If we need to do "cleanup" why can't we learn from our big brother CPython and have sprints to focus our development efforts.... this might uncover resoucing issues, but that's what needs to be done to clean out the cobwebs...no? Although a great product...as a OS project there's plenty of tricks we should try to pick up from projects that are getting the resouces, the funding, the sponserships... Regards, Walter > >well, I think people underestimate how difficult to maintain the >codebase is, it takes a lot of time to absorb enough of it such that >making changes does not too easely >break things or subtly change the presented behavior. > >So its cleanup, which of course is a delicate thing in itself, is a very >important priority. > >Also CPython is not going to slow down for us, being ruthless at >prioritizing is central. -- Simplicity--the art of maximizing the amount of work not done--is essential. from: http://www.agilemanifesto.org/principles.html |