> Another reason for qooxdoo's slow adoption might be the strong control of > 1&1 over its development. It's not the road traveled by most open source > projects. In most successful open source projects, even if there are some > core developers, there is an easier mechanism in place to integrate source > code from external developers, which then gets maintained by the qooxdoo > team/developer community. From what I can tell, this mechanism is less > open for qooxdoo than it is for other projects. Committing to a framework > on which they feel they have less influence than they have on other open > source projects might scare off some larger potential users, for which > strategic decisions are not taken easily or light-mindedly.
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. T. ------------------------------------------------------------------------------ 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
