On Thu, 17 Jun 2010, Jean-Baptiste BRIAUD -- Novlog wrote: > On 17 juin 2010, at 07:55, Fritz Zaucker wrote: > >> Good morning, >> >> On Thu, 17 Jun 2010, Jean-Baptiste BRIAUD -- Novlog wrote: >> >> 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. > > How potential user will know Qooxdoo had been developed in the right > direction?
Looking at the features ... > Also, you may not "need" a large user base, that's fair enough, and we may > be "special", but increasing user base will facilitate Qooxdoo adoption by > our customers. Your customers seem not to trust you in selecting the right solution. This means, that they are playing in your bath-tub instead in their own (they should tell you what the problem is, you are the expert for the solution). >>> 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? > > One person problem : too much work, not community driven. Only too much work when there are too many contributions. > Several person : less work, community driven, more fun : create contact, > team building, community building. That is very important. That might be important, but is a different topic. > Also, who would be that one person ? Core team from 1&1 ? They already do > not have all the time they would like to have. Hopefully, we already know > committee process can be done : see Apache or Eclipse or Linux or ... Somebody could contribute this work ... >> Having a committee just adds all the overhead you describe and in the >> end, nobody is really taking responsiblity. > Thats why I had thought to 3 to 5 people taken from CC to be the head. As > I said there need to be people "in charge", so I agree with the risk but I > thing it is taken A committee just adds more work with little benefit. And finding one (or one per area) capable person is certainly easier than finding 3-5 (times n for each area). >> This person would have to do only a few things: >> >> >> - Decide, if a contrib is "valuable"? > How one person could decide value of contrib on so different technos ? > >> >> - Make sure, the contributor follows the guidelines (docu, etc) > > Exactly, but this take time ! Are you aware that this mean read all code > in various languages (Lisp, Java, javascript, ...) of all contribution for > one person ? This is not doable by one person. As I said, one person per topic would be an option. 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
