Peace people! This isn't about saving the world or anything. My 2c on the issue is that as long as the projects are not released, they are fine in whatever state they are. There is no contract on the code quality for the wicket-stuff projects, and even without much documentation etc, they can give people nice idea's when they check out from CVS - that's the more 'power user' type.
I think at the moment such a project is released, there should be at least one person be stepping up and taking responsibility for the project. I can live with less documentation/ lower standards even in that case, as long as it is (made) clear that these projects are contribition projects, and any issues should be addressed to the person (or list) repsonsible for that project. We (wicket core devs) do want to help with setting up the projects etc (and in fact we did quite a few times), but we don't want to be responsible for maintaining them. So, yes, there are a couple of projects in there that were started, but were never really finished/ polished. IMO, that's fine as long as they are not released and/or it is clearly stated why they were left unpolished (like the fValidate project). Furthermore, about that code quality... really, I take a look at some OSS project almost every week (which usually means I'll check it out and try to read and understand the code), but most, I repeat most of these projects aren't doing that well at all in the field of docs and architecture. There are a couple that actually are good, and they are usually the succesful ones, like Hibernate, Spring, XFire, etc. But even the succesful ones (and even some JCP ones!) aren't allways that polished. I don't get where the notion comes from that Wicket does bad in this field. Though improvements can always be made, I think we really aren't doing that bad at all. Eelco On 10/16/05, Gili <[EMAIL PROTECTED]> wrote: > Igor Vaynberg wrote: > >> By poor design, I mean it sometimes looks some of the > >>code was created as a prototype and when it was complete no > >>one went back to refactor it. > > > > > > Code design is very subjective. Why don't you provide us with concrete > > places where you think refactoring needs to be done. > > I did and you didn't like it so I dropped the issue and moved on with > my life. > > > You have been told over and over again that you are more then welcome to > > provide patches for javadoc or any other documentation. So far I havent see > > any... > > > You still don't understand that this is a community effort and we do > this in > > spare time of which we have very little. Do you think I would rather > write > > javadoc or spend time with my wife and my daughter? So instead of > bitching > > about it why don't you contribute! > > I can't read other people's minds. It is impossible for me to write > Javadoc for code I do not understand. Some code I can easily pick up, > reverse engineer and document. Other code is simply beyond that and the > other person who can realistically get this done is the original author. > Now, I understand your priorities and I respect them, but at the end of > the day: > > 1) The code is still under-commented > 2) I can't read your mind > 3) I suspect no one else can either > > Either someone who understands it should document or someone should > rewrite the entire module from the ground up and document *that* > properly. The latter seems like wasted effort but if we have no other > choice this is something we should consider doing. > > I'm currently preoccupied with issues below the wicket layer so I > can't > contribute to them at this time. I might not even end up using the > Hibernate module at all depending upon how things work out. > > Gili > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Wicket-develop mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-develop > ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
