Your SlideShare is downloading. ×
0
Community Leadership Summit - Calistoga March 2013
Community Leadership Summit - Calistoga March 2013
Community Leadership Summit - Calistoga March 2013
Community Leadership Summit - Calistoga March 2013
Community Leadership Summit - Calistoga March 2013
Community Leadership Summit - Calistoga March 2013
Community Leadership Summit - Calistoga March 2013
Community Leadership Summit - Calistoga March 2013
Community Leadership Summit - Calistoga March 2013
Community Leadership Summit - Calistoga March 2013
Community Leadership Summit - Calistoga March 2013
Community Leadership Summit - Calistoga March 2013
Community Leadership Summit - Calistoga March 2013
Community Leadership Summit - Calistoga March 2013
Community Leadership Summit - Calistoga March 2013
Community Leadership Summit - Calistoga March 2013
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Community Leadership Summit - Calistoga March 2013

719

Published on

These are the slides of team 3 at the Community Leadership Summit in Calistoga (at the Open Source Think Tank). Our group discussed the topic "Developer Growth", answering questions such as: How will …

These are the slides of team 3 at the Community Leadership Summit in Calistoga (at the Open Source Think Tank). Our group discussed the topic "Developer Growth", answering questions such as: How will you attract new developers to participate? How will you retain developers so they become significant and sustained contributors? How will you attract new demographic of developers, outside of the current industry? How will you encourage existing partner organizations to contribute developers to the project? How will you deal with organizational requirements (e.g. NDAs, copyright assignment, re-licensing requirements, etc)? How will you keep developers motivated and feeling they have a sense of personal influence on the project? How will you avoid entitlement?

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
719
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. ATTRACTION How do you get developers to join?
  • 2. ORGANIC ATTRACTION Make sure your product takes away a pain • People usually don’t contribute to products they don’t use • Corporations don’t adopt code they don’t need Provide good tooling: • Guidance: e.g. Mozilla’s open TODO list • StackOverflow • Manuals (people aren’t going to use your product if they don’t know how) This works best if you create a niche: FOCUS!!! • Be the leader in your field of expertise
  • 3. Go to the place to be for developers Engage people!
  • 4. Provide free documentation By example tutorial base on the many code samples written in answer to questions. TRAIN PEOPLE TO USE YOUR PRODUCT AND THEY WON’T GO LOOKING FOR ANOTHER SOLUTION
  • 5. Write books (or have them written) 1st Edition: 2006 • 11.500 copies 2nd Edition: 2010 • 7.500 copies
  • 6. CULTIVATED ATTRACTION Organizational engagement: • Acknowledging, registering, rewarding contributors Including new demographics: • How to broaden your reach? Individual recruiting • Hiring key people
  • 7. Community and development
  • 8. Document your IP CLA
  • 9. Remember the contributor’s name! On payroll Contractor Volunteer
  • 10. Engage new demographics • Port to other technologies; interoperability – E.g. Java to C# – Allow using a C library in PHP • Write white papers for specific verticals – Financial sector, government,… • Translate manuals in German, French,…
  • 11. RETENTION How do you keep developers interested?
  • 12. Recruit / Share the wealth • Rewards that make people more involved • Invite to a conference for free • On payroll • Use different roles: answering questions, first commits, code reviewing • Make sure there’s some redundancy: e.g. code reviewer can step in when a developer disappears • Freelance assignments • For third parties • For product enhancements
  • 13. Recruit / Share the wealth • Create win-win partnerships • Thou shalt not compete with thy customer. Allow integrators to make money • NDAs: – Don’t ask people to sign an NDA – Sign an NDA when people ask you to • Make sure that developers changing jobs continue using the product
  • 14. Responsibility • Increase / reduce responsibility – People deserve / earn responsibility – Make sure that the responsibility isn’t crushing: due to whatever reason somebody can drop out for a while • Responsibility towards the user – Developers can get carried away and create code nobody will ever need – Corporations can get carried away making it the user impossible to use the product
  • 15. WHEN IN CALISTOGA Why is there grass in-between the vines? The grass is there to improve the quality of the wine. It protects against weed, erosion, diseases,... Moreover, competition from grasses is also a natural and efficient tool to control yield. Reduction of grape yield is necessary to increase sugar content (higher alcohol potential) and content of favorable flavors. Companies need communities for the same reason.

×