On 23/08/05, Kervin L. Pierre <[EMAIL PROTECTED]> wrote: > I know I'm going to step on toes by saying this > but... > > James does not need more code before James needs > management and design.
I don't think you are being overly critical, but I do think you are oversimplifying the situation. James has had a stable and consistent design for a few years, it is well understood by the commiters, and the future of James has been discussed over and over. What we have lacked is people with the time to expend on reaching our goals. Stefano is not "doing his own thing" we have elected him to join us because not only does he understand James, he also understands our direction and has demonstrated his ability to adapt his point of view when the group disagrees with him. What I am in favour of is encouraging people to return to the propose, commit, review approach we have traditionally taken. This may result in a longer cycle between stable major versions but it does not diminish quality, what we have to ensure is that the review is conscientious, and that we take the time to reach consensus of approach. > I hope I am not being overly critical. I have > had high expections of James. Especially being > an Apache project and all. In what way does James fail to meet your high expectations? d. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
