On Fri, 2010-10-08 at 09:24 +0200, Tomeu Vizoso wrote: > If we are going to make an effort to revive a team, I would consider > reviving the community team first so we can improve our chances of > covering the dozens of other important positions we have vacant right > now.
True, but I've always had trouble figuring out what the coordinator of the Community Team would actually do. Community "management" is such an ethereal thing that it's hard to frame it into a separate team coordinator. I do my own share of community management by inviting people I meet (whether in person or electronically) to join the project at some level. Being welcoming to newcomers is the duty of every Sugar Labs member. Mel and Frederick have led some initiatives to lower the barriers to entry. Marco has been working on the same problem, from the development perspective. There were really good recommendations in their blog posts. If we formalize their work, it'd better be a horizontal role with enough authority to make the necessary changes happen across all teams. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ _______________________________________________ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep