> > We did a comparison internally, but no one was better than Qooxdoo for > > the purpose of real web application development (RIA). It has a better > > design and is faster than most of them. Most of the ideas are close to > > how Java has been designed. In some cases it is better designed. One > > negative thing is that Sebastian has opened up the software, but not as > > much as it deserves. It slows development too much. It must be changed > > in some or the other way, else dedicated and brave developers will > > choose other libraries to support and contribute. > > IMHO qooxdoo problem is not political if we should really have one. > Please tell me what exactly you mean with "has opened, [...] but not as > much as it deserves." What are your ideas, Kent? Give this discussion > some real facts - not just try to put some public sentiment.
I have only been using qooxdoo for about a month, so take what I'm going to say with a grain of salt. Kent is IMHO in a way right. AFAIK qooxdoo has been mostly developed in house and it wasn't until pretty recently that it was made free software. Developing stuff in house is very different from developing free software. It is true that qooxdoo is a great product and it will probably continue to be a great product. But that isn't what Kent is talking about, it is that qooxdoo could be EVEN BETTER! But for that to happen some development processes need to change. They need to be in harmony with how the community works. Otherwise everyone will just be frustrated. Contributors because their patches aren't committed and you and your team because the mailing list fills up with ungrateful and unhappy users. Sure, it is possible to continue that way with an in house development process, but I bet correctly channeling potential contributors skill into qooxdoo can be much more efficient. For example, a BUG TRACKER!!!! It is a vital tool to enable the community to help you. I have reported issues on this mailing list with qooxdoo that was already known about. If there was a bug tracker I could have checked myself if the issue was reported and would have avoided wasting my time. Potential contributors to qooxdoo could look at the bug list and find some easy problem and fix it. Thereby reducing the work that you have to do. Another way to use the free labourers that are volunteering on the list is to appoint some people and let them do menial tasks. I nominate Kent because he seem to wanna. :) The idea is to have some kind of informal training program with students that graduate by getting svn commit access. You are probably right that there are no devs here except for you and your team that know enough about the qooxdoo core to be able to work on it efficently. That doesn't mean those people are entirely useless to qooxdoo. Qooxdoo is severely under documented, it doesn't take a core developer to write API documentation. Anyone with a little training and some urge could do that. The same thing with the examples in the demo directory. Appoint someone to help you write new demos and stuff. Do the same with patch reviews, someone that you trust can comment on code that people submit for inclusion. Everyone knows how boring that is, so it's perfect for an aspiring developer. Everyone starts from the bottom and work their way up. :) Let me also state that I don't think there is anything wrong with how Sebastian is running the project now. BUT it is possible for him to run it more efficiently. And also, it is obvious that many of us discussing here do not have English as their native language. We shouldn't let minor communication problems ruining the collegial atmosphere. We ALL think Qooxdoo rock. :) -- mvh Björn ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
