|
|
| Line 1: |
Line 1: |
| ==Feb 8, 2010 Meeting Notes== | | ==Feb 15, 2010 Meeting Notes== |
|
| |
|
| * Weekly dial-in meeting, Monday, 8 a.m. PST | | * Weekly dial-in meeting, Monday, 8 a.m. PST |
| Line 16: |
Line 16: |
| * '''Get Involved!''' | | * '''Get Involved!''' |
| * Kudos and thanks | | * Kudos and thanks |
|
| |
| * Featured Project presentation: "Stop Badware"
| |
| ** Max Weinstein
| |
| ** Max's slide presentation: http://bit.ly/dnPUH6
| |
|
| |
| * What can Mozilla Drumbeat learn from Cambrian House?
| |
| **Shelley Kuipers, President & CEO www.chaordix.com
| |
| **http://www.slideshare.net/jrcorke/mozilla-overview
| |
|
| |
|
| * Web site update | | * Web site update |
| ** Matt | | ** Matt |
| ** http://drumbeat.stage.mozilla.com/ | | *** + Paul, Gerv, Mike? |
|
| |
|
| * FOSDEM update | | * FOSDEM report-back? |
| ** Mark | | ** Mark |
| ** http://fosdem.org/2010/ | | ** http://fosdem.org/2010/ |
|
| |
|
| ==Meeting Notes==
| | * Your item(s)? |
| | |
| Questions for Max
| |
| 1) participate in helping to develop platform
| |
| 2) participate with stories
| |
| | |
| Max:
| |
| * these phases may overlap | |
| * no reason people can't share stories even if platform and tools aren't already in place
| |
| | |
| Cambrian House launched 2006
| |
| best web-enabled software
| |
| 50,000 members
| |
| 7000 ideas
| |
| ran ad campaigns to draw folks
| |
| active community management
| |
| | |
| activities that would draw a larger crowd
| |
| contests / "Tournament of Champions"
| |
| test to see if the market wanted that product or service
| |
| follow-on investing with that entrepeneur or idea team
| |
| then could go to market with that help
| |
| | |
| comminty drove three things:
| |
| 1) collective intelligence / wisdom on best ideas
| |
| 2) production. people joined various teams to help build. included maintenance of own web site and community.
| |
| 3) enabled commerce transactions between members. transactions between community members. own currency. Also "royalty points", to graft or gift royalty points between members.
| |
| | |
| Slides:
| |
| http://www.slideshare.net/jrcorke/mozilla-overview
| |
| | |
| give right construct or direction to community
| |
| | |
| threaded commenting: mostly about a dialogue between the crowd and the person who submitted their idea
| |
| | |
| successful project:
| |
| "mob for hire"
| |
| successful business
| |
| a lot of people found others that they started businesses with and form friendships with
| |
| | |
| the idea of crowdsourcing is overwhelming for many people
| |
| hand-holding along the way
| |
| breaking into smaller tasks / milestones
| |
| | |
| different methods of recognition are important
| |
| | |
| they ran a weekly community blog
| |
| video discussion of ideas submitted that week
| |
| what was best ideas, etc.
| |
| live critique of ideas, etc.
| |
| drove a TON of community participation
| |
| | |
| Q: Do you always award points for any participation?
| |
| | |
| Had a point system for participation points, glory points, royalty points, and exchange of currency between members
| |
| always award points for any type of participation between members
| |
| main way to get glory
| |
| different things motivate different people, and different levels of commitment
| |
| | |
| Q: When you set up, did you look at motivations?
| |
| | |
| First started, were just interested in awarding people money
| |
| Started several different projects (like "greedy or needy") purely motivated by recognition types
| |
| Took a while to figure out. Looked closely at gaming theory.
| |