Hej Stefan, let me finally comment on your suggestions now that the releases shipped successfully.
From: Stefan Andersson [mailto:[email protected]] > 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. We're not giving up on the current setup of mailing list assistance. A dedicated person would introduce a bottleneck and a single point of failure, also decouple the framework developers from the community and their ideas and needs. > Most questions and answers are quite trivial and can be handled > by one person. In fact many questions already get answered by fellow community members, not the core team, and the community is encouraged to self-service their peers even more. Particularly answering some easier questions is a great way to get newbies into the project and become active users. > 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. As explained it is by intention to involve the framework developers in the communication with the community. This kind of diversity should be seen as a feature, reflecting the open source community with its mailing list, rather than a streamlined support forum. > 2. the same person shall also be a dedicated "contribution quality" > representative going through the contributions and > quality test them. It's the genuine obligation of a contributor to ensure his/her contribution is of high quality. IMHO delegating the task to an "outsider" to test and polish a contribution wouldn't be effective or fair, also doesn't scale. There certainly is reasonable support (by core team and/or community) for contributors to improve in delivering good-quality software, and the user feedback should also tell. > 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. I think the most vivid community is with users, contributors and core developers helping and supporting each other. In fact many contributions improved by collaborations among users, not involving the core team. Nevertheless the core team has always been trying to specifically support contributors, helping out, answering questions, etc. > 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. It's fine to propose such contributions by the contributors themselves, without a specific spokesperson. The core team and tech lead will certainly look into it. Keep in mind, though, it is not the intention to retrofit contributions into the framework, but to allow for an ecosystem of contribs around the framework package itself. > 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... For sure, everyone of the core team would be a great representative. ;-) But I hope it became clear that we don't want to introduce such a single-person bottleneck. It wouldn't improve the current, much appreciated model without introducing many sincere drawbacks. Andreas -- Andreas Ecker Project Lead http://qooxdoo.org ------------------------------------------------------------------------------ Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
