Good morning, On Thu, 17 Jun 2010, Jean-Baptiste BRIAUD -- Novlog wrote:
> If I understood correctly what Thomas said, your pretty much satisfied > with 1&1 internal demand. So, user base won't really increase. I didn't understand it like that. > Nothing to add on that point which is my main concern about Qooxdoo. User base is not the point. If Qooxdoo develops in the right direct and stays as mature and stable as it is, I'll be happily write applications with it for our customers. > 4. contrib : help by giving code to Qooxdoo community. > This could be improve by organizing contribs, creating a committee where > people is in charge or sorting out contribs, > attach to them a state (mature to young), test (does it work with latest > Qooxdoo version, ...) > I think this committee should not be 100% 1&1. Maybe 50% 1&1 and 50% > community. > That CC (Contrib Committee) should also be structured in area of expertise of > its member. > * area1 : widgets (HTMLArea and others, ...) > * area2: : build, IDE, ... (qxbuild, qxtransformer, ...) > * area3 : backends > * area 3 subareas by techno : PHP, js, Lisp, Java, ... > > I'm volunteer for area 3 Java subsection. > > CC would also need : > * a specific mailling list > * a decision process (like Apache incubator -> ... -> ... -> main validated > project) > * 3 to 5 people taken from CC and maybe elected by CC members for 1 year. > There need to be some people "in charge" if that has to work efficiently. What's wrong with ONE person being in charge of managing the contribs? Either all of them, or, if it's too much, one person per area? Having a committee just adds all the overhead you describe and in the end, nobody is really taking responsiblity. This person would have to do only a few things: - Decide, if a contrib is "valuable"? - Make sure, the contributor follows the guidelines (docu, etc) - Classify contribs (compatibility with Qooxdoo versions, maintained/unmaintained) - Remove stuff that is no longer relevant > On a more technical point of view, including a contrib is still too > complicated and risky for users : > * what happen when Qooxdoo deliver a new version ? > * how do I know a new contrib version is done ? > => something like linux apt for contrib would be great. > * contrib state (working, experimental, ...) , what a contrib is doing, lack > of doc, ... can be hande by contrib committee. That would be useful. Cheers, Fritz -- Oetiker+Partner AG tel: +41 62 775 9903 (direct) Fritz Zaucker +41 62 775 9900 (switch board) Aarweg 15 +41 79 675 0630 (mobile) CH-4600 Olten fax: +41 62 775 9905 Schweiz web: www.oetiker.ch ------------------------------------------------------------------------------ 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
