Hi Stefan,
I think you have a good point that the contribution system should be improved.
We already had a discussion about that as well. But I don't think this problem
will be solved by a full time supporter.
We have plans to introduce a central register to add contributions (you can
think of it like npm). All contributions will be hosted by the contributor
(e.g. at github) and can be registered at some central place. Anyway, we don't
know yet how this will look like.
Have a nice day,
Tino
Am 08.12.2011 um 08:33 schrieb Stefan Andersson:
T!
Eclipse is a tough regimen but it apparently has worked very successfully
during the years. I guess if measured, they have produced more quality code per
hour than qooxdoo, definitively involved more people and then mainly due to the
fact that they delegated it on more hands.
I agree on lack of resources limits and this is a management decision what way
to go. But your very conservative way to go can be criticized or at least
reflected upon. There is no need to defend your position. It is just a decision
like any.
We think that the contrib idea is a good way to bridge this problem and
increase contribution code access, but it needs to be developed further to
embrace the community and push the community to start using the code
contributed.
But to be more creative in this here is our suggestion:
1. dedicate 1 person to answer all questions or at least most (>90%) questions
on the list. Now all of you are doing it, which I think is a waste of resources
and focus. Most questions and answers are quite trivial and can be handled by
one person. He can also be the mediator. At the same time you get one spokesman
of the core team instead of several like now. Many persons many ways of
communication. The other will be more effective producing code.
2. the same person shall also be a dedicated "contribution quality"
representative going through the contributions and quality test them.
3. the same person shall be a development assistant to the contributions, a
spokesman for the core team, and a helper to solve technical issues with the
contributions and ideas and visions of changes of the packages. This creates a
vivid community.
4. the same person proposes, when ready, to the core team contributions to be
included to the core and participate in the decision of it.
5. Pick one of you! Tino has shown to us to be the most diplomatic, polite, not
polemic and most service oriented representative of yours so far. I am not
saying that the others are not...
This I believe will all increase the quality and credibility of the
contributions like in dojo and others.
Stefan
------------------------------------------------------------------------------
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and point of
discussion for anyone considering optimizing the pricing and packaging model
of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/_______________________________________________
qooxdoo-devel mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Tino Butz
Mobile Architect
1&1 Internet AG - Web Technologies
Ernst-Frey-Straße 9 · DE-76135 Karlsruhe
Telefon: +49 721 91374-4488
[email protected]<mailto:[email protected]>
Amtsgericht Montabaur / HRB 6484
Vorstände: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Robert Hoffmann,
Markus Huhn, Hans-Henning Kettler, Dr. Oliver Mauss, Jan Oetjen
Aufsichtsratsvorsitzender: Michael Scheeren
------------------------------------------------------------------------------
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and point of
discussion for anyone considering optimizing the pricing and packaging model
of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
