I prefer the current way. If only one person deals with support questions, this person will be mostly absorbed doing this (and the other more administrative issues you mention) and will become disconnected from coding and thus less competent.
We have been quite happy with having the responsibility to deal with our request tracker rotate on a monthly base. The person responsible answers questions directly, if possible, or otherwise dispatches them to others in the team. This is more efficient than everybody reading all requests. But I don't think it is very helpful to permanently come up with management suggestions for the core team from the outside. There are always many aspects that are not visible and I think Andreas and his team are doing a good job. And to be honest, it gets a bit on my nerves, that you, Stefan, are not even willing to tell who and where you are and what you are working on, are permanently criticizing the way 1&1 is going. On Thu, 8 Dec 2011, Stefan Andersson wrote: > 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 -- 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 ------------------------------------------------------------------------------ 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
