Is it time for a user survey?
Opened this issue · 2 comments
Big open source projects run surveys to find out who the users are and some of their needs.
Now that the handover to the osquery foundation is settling down, it might be a good idea to run a survey targeting our users.
AFAIK, TrailOfBits are the only ones who have done any kind of research like that, but it was private/targeting their customers.
- https://blog.trailofbits.com/2018/04/10/what-do-you-wish-osquery-could-do/
- https://www.youtube.com/watch?v=k7AKxFIujjY
Some things we might want to know
- How many organizations are using osquery
- Average size of fleets
- Where is data being sent to?
- What works well, what doesn't.
What tools to use to build a survey?
- qualtrics; it's used by the Go team for their yearly survey. Others?
Leave your thoughts below and I'll edit the issue over time.
AFAIK, TrailOfBits are the only ones who have done any kind of research like that, but it was private/targeting their customers.
FWIW We surveyed the ~6 most active osquery users from the osquery Slack, some of which were our clients and others who were not.
This is a great idea! I feel like we should brainstorm a list of topics that folks can judge working/not-working, to make that less open ended. The survey can then conclude with asking open ended feedback.