Hi flj, thanks for your feedback.
On Sun, 2010-06-20 at 23:28 +0200, [email protected] wrote: > > What OS projects are you thinking of? For Python, Guido van Rossum is > > "benevolent dictator for life", and last time I checked Linus Torvalds > > still oversees the patches to the Linux kernel. Larry Wall probably has > > the last word about core Perl, and Slava Pestov certainly determines the > > direction of Factor. Other projects like Eclipse and Apache are officially > > committee-driven, but I'm not sure how strong e.g. the influence of IBM is > > in these committees. So, having an "ultimate authority" is not unusual for > > such projects. > > Surely Linus Torvalds and a few of other core developers of the Linux > kernel oversee all patches. But on one hand they're not all hired and > sponsored by the same company, on the other hand they mostly oversee > patches and other contributions, rather than writing all the code > themselves. This is IMO an essential difference. I think the situation is pretty similar, especially when comparing to other extremes, e.g. closed-source solutions like MS Windows or Mac OSX. As with Linux, if there are high-quality contributions to qooxdoo, they certainly get reviewed and eventually be integrated into the framework, just like it has always been done. > I can see reason behind the decision not to integrate contribs > indiscriminately into the qooxdoo codebase. Sure, the existence of a contribution cannot automatically mean it would become part of the framework codebase itself. That would certainly be a wrong expectation, also as we take special care in maintainability. Of course, any of such contributions should at least be able to become part of the qooxdoo ecosystem and therefore be available to everyone interested. > I and the company I'm working for have no problem with 1&1 being in > charge of qooxdoo. We are too small to add significantly to qooxdoo - > we simply don't have the required resources. Adding to a discussion like here or blogging/telling others about qooxdoo is also a welcome contribution to this project, thanks. ;-) > What I meant to say is that some larger companies might have a > problem with using a framework to which they can't easily/more > liberally add their contributions, and thus at least partially > influence the general direction of development, but over which a > company being a potential competitor has all the authority. Eclipse is > open source, and so is NetBeans. Do you think IBM will ever use > NetBeans, or that Sun will ever use Eclipse as a standard IDE for > their developers? So this an example of non-collaboration between competitors? Hard to see how this would map to real-life scenarios for qooxdoo. I think that whoever the contributor is, it should at least be possible within an inviting ecosystem. > There's a huge opportunity here for both 1&1 and qooxdoo, IMO. Sun > managed to get Java where it is now because there was nothing like it > at the time Java arrived, among other reasons. Qooxdoo doesn't have > that much of an advantage, but still, all other potentially competing > frameworks are a lot less programmer-friendly, and don't abstract the > browser that strongly. Marketed the right way, I think qooxdoo has a > good chance to become a hit, and the de facto standard for next > generation web apps (just to use a few empty big words). For this, > however, big players have to become convinced that qooxdoo is open to > them on the long term, and not just free. Otherwise they won't put > their weight behind it. If people think qooxdoo is a powerful and somewhat special framework, there are many ways to contribute and to make it more popular. It's much appreciated for instance that users blog/write/talk about it, which are essential additions to our own activities. More widespread adoption would certainly be great, who would be against it (the scope and comprehensiveness being limiting factors compared to smaller libraries targeting simpler topics). It doesn't necessarily mean there need to be other "big players" behind it. Of course, we're always interested in discussing potential collaborations. As it is, qooxdoo is the free, open source JavaScript framework provided by 1&1, similar to other company-sponsored ones like YUI by Yahoo or GWT by Google, but IMHO with much better opportunities for involvement and collaboration in an open-source mindset. YMMV. Bye, Andreas -- Andreas Ecker Project Lead http://qooxdoo.org ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
