6. How many of those people are writing code with Catalyst? If there are non Catalyst coders on your team, how many of the whole team would you like to be writing Catalyst code?
7. How many people using Catalyst on your team are subscribers to the Catalyst mailing list?
8. How many people writing Catalyst code on your team use the #catalyst IRC channel on irc.perl.org?
9. What do you see as potential for growth of Catalyst in your organisation? How many people do you think will be using Catalyst in your organisation in 12 months? In 2 years?
12. How many of those people are writing code with Catalyst? If there are non Catalyst coders on your team, how many of the whole team would you like to be writing Catalyst code?
13. How many people using Catalyst on your team are subscribers to the Catalyst mailing list?
14. How many people writing Catalyst code on your team use the #catalyst IRC channel on irc.perl.org?
15. What do you see as potential for growth of Catalyst in your organisation? How many people do you think will be using Catalyst in your organisation in 12 months?
19. Best practice: Send out three reminders Our practice: Send out no reminders Best practice: Concentrate on hard to reach groups Our practice: Just collect data quickly Step 5. Wait for responses
21. Number of potential respondents Asked for one response per team. Median team size 4, 1000 mailing list subscribers 88% of teams have 2 or less subscribers
25. Correction for Non-Response Bias (this is a technique from marketing) Solution: Pull numbers out of the air. 50% inflation? 100% inflation?? Run another survey with more aggressive recruitment to get a better estimate of NRB
26. Final estimate We know about 3400 users connected to subscribers. We know that this is at least a 20% under-estimate