Hi, Carsten Munk wrote: > The questions are: > > * What are you waiting for to happen in the MeeGo project?
I'd like someone clearly in authority to ask for input for community policies. Some policies that come to mind: * Sysadmins - initial sysadmins, policies for managing meego.com resporces (separation of community & private data, for example) and how new members can join the team * Web team * Wiki editors * Requirements before community software can be hosted on meego * Code of conduct and posting guidelines for meego.com resources * Criteria for having a blog aggregated For teams in general, who are the initial members, and how can new members join. I think similar policies could be worked on for things like commit access to various branches of source code, and the workings of non-development teams like l10n, documentation, design, community marketing... > * Do you know what is currently blocking these things to happen, if so, what? Right now, I don't feel empowered to lead the charge for any of these things. I'm not a person clearly in control of any of these resources. And I don't know who is. Putting names to teams would be a huge help. > * What would you contribute with if these things happened? What area, > what specific things - how can you help, where's your talents in this > area and interest? My specific areas of interest are related to the infrastructure we put in place to allow new community members to gain the trust of old community members without getting in the way too much :) Documentation, wiki management, elections, event organisation... Cheers, Dave. -- maemo.org docsmaster Email: [email protected] Jabber: [email protected] _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
