Community Office/Meetings/Brainstorming 12-7-10

Revision as of 16:43, 2 December 2010

Reminder: Community Office Goals for 2011

• Get more people actively contributing to the MeeGo Community (code, application developers, documentation, community facilitation, other participation - technical and non-technical) - more details
• Better marketing and promotion of MeeGo - more details

How can we make the community office meetings more productive / useful?

• So far, I don't think we're really accomplishing much in these meetings. How do we use this meeting to accomplish our goals (see above)? --Dawnfoster 16:42, 2 December 2010 (UTC)
• Add your idea / comments here (with signature / timestamp)

Community Office task lists - what works / what doesn't?

• The idea behind creating proposed / committed task lists was to avoid duplication (multiple people working separately on the same projects) and get more people working on tasks that we needed to complete, but it seems to have just created a barrier to participation. I was hoping that the task lists would give people tangible things to work on, but other people aren't really volunteering to take on new tasks. Should we scrap this whole idea and do something completely different? Should we take what we have and make some changes? --Dawnfoster 16:42, 2 December 2010 (UTC)
• Add your idea / comments here (with signature / timestamp)

How can we get more people contributing to the MeeGo project?

• We have a Contributing to MeeGo document and the CO task list but they don't seem to be helping much. What else can we do to get more people involved? Do we need better incentives (what kind)? --Dawnfoster 16:42, 2 December 2010 (UTC)
• Add your idea / comments here (with signature / timestamp)