2011 Alfresco Community Survey Results

1,874 views
1,801 views

Published on

Results of the 2011 Alfresco Community Survey with some light commentary.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,874
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
23
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

2011 Alfresco Community Survey Results

  1. 1. 2011 Community Survey Results<br />Jeff Potts<br />
  2. 2. Initial insights -- General<br />Nice global reach: ~70 countries<br />Top industries: High-tech, Professional Services, Government, Education, Finance<br />~25% of survey takers started but did not finish. Maybe make it shorter?<br />
  3. 3. Initial insights -- Events<br />>50% of respondents would attend a local meetup if one were available<br />DevCon Europe shaping up to be twice the size of DevConAmericas if everyone from the survey attends<br />
  4. 4. Initial insights – Alfresco.org<br />Forum tone isn’t a problem, but helpfulness is a big problem<br />Wiki question indicates the find-ability of the wiki is okay<br />But LOTS of feedback on confusion around version applicability<br />People want to see more blog posts and articles from Engineers and Community Contributors<br />
  5. 5. Initial insights – Community engagement<br />Surprisingly high number of people use the wiki to find community code contributions. Should use that as an interim until an index is in place<br />Large number of people who have never leveraged a community code contribution. Needs further analysis<br />Need to flatten the learning curve for contributors<br />
  6. 6. Demographics<br />
  7. 7. Relationship<br /><ul><li>Large number of evaluators due to who we included in our email blast
  8. 8. Over half are technical</li></li></ul><li>Experience<br /><ul><li>Roughly split between <1 year and >1 year</li></li></ul><li>Country<br />
  9. 9. Industry<br />
  10. 10. Version<br />
  11. 11. Events<br />
  12. 12. Existing local event<br /><ul><li>Half of the community doesn’t have a regular local meetup to attend…</li></li></ul><li>Would you attend a local event?<br /><ul><li>…but half of those people probably would attend if one was available</li></li></ul><li>Past events attended<br /><ul><li>Lots of webinars and lunch-and-learns matches up with “evaluators”
  13. 13. Should filter out evaluators to see if this changes</li></li></ul><li>DevCon<br />
  14. 14. Alfresco.org<br />
  15. 15. Keep informed<br />
  16. 16. Tools used to stay informed<br /><ul><li>Social channels surprisingly low
  17. 17. Twitter outranks LinkedIn and Facebook, which makes sense</li></li></ul><li>Previous forum activity<br /><ul><li>Evaluators probably skewing the numbers here</li></li></ul><li>Forum helpfulness<br /><ul><li>We could improve a lot here. ~45% not receiving a helpful response seems way too high</li></li></ul><li>Forum tone<br /><ul><li>Looks like we are well-behaved for the most part.</li></li></ul><li>Open-ended “forum” question<br />Answer questions (15.6%)<br />No changes needed (12%)<br />Improve Alfresco responsiveness (11%)<br />Improve search (6%)<br />
  18. 18. Wiki use<br />
  19. 19. Wiki find-ability<br /><ul><li>Glad people are finding what they are looking for.</li></li></ul><li>Open-ended “wiki” question<br />Updated content (16.1%)<br />Version info (11.7%)<br />Code examples (9.3%)<br />No changes needed (9.3%)<br />Better organization (7.5%)<br />Better documentation (6.7%)<br />Better search (4.9%)<br />More technical (4.7%)<br />Local language (2.6%)<br />
  20. 20. Blog voice<br />
  21. 21. Community Engagement<br />
  22. 22. Past community contributions<br /><ul><li>Forums and bugs are how most people contribute followed by blogs, social, and presentations
  23. 23. Deeper engagement happening less often</li></li></ul><li>Finding contributions<br /><ul><li>Need to make sure cool contribs are linked to from the wiki and the forums!</li></li></ul><li>Types of code contributions leveraged<br /><ul><li>Shocking how many people have not leveraged a code contribution
  24. 24. Language packs, code snippets, and dashlets are big</li></li></ul><li>Why contributions weren’t leveraged<br /><ul><li>Should filter out evaluators on this
  25. 25. Lots of people don’t know where to look or couldn’t find something that met their needs
  26. 26. Significant number of “not invented here” responses</li></li></ul><li>Code contributions planned<br /><ul><li>Large number of people that can’t/don’t want to contribute
  27. 27. Need to find a way to help people share code snippets</li></li></ul><li>Code contribution hurdles<br /><ul><li>Need to flatten the learning curve for contributors</li></li></ul><li>Open-ended “vibrancy” question<br />Better documentation (6.19%)<br />More plugins/extensions/integrations (5.73%)<br />Answers in forums (5.5%)<br />Local events & meetups (5.5%)<br />More marketing/comm (4.82%)<br />Fix my product issue (4.59%)<br />

×