Some of you might remember when Andrew Starr-Bochicchio send out the Developer Advisory Team’s analysis of the feedback new contributors gave us. It was a great read, told us a lot about how new contributors get involved, but it was a also quite a bit of work.
As we conducted most of our interviews via mail, we had lots of answers in our inbox. As a team, we put them into a Google Doc and after the release cycle had passed, we had amassed 6 months worth of feedback. Sometimes just a few lines which concentrated on just one topic, but sometimes heaps of text covering each and every point of their developer experience.
As we feel this was quite a bit of work, but also worth doing, we want to continue this effort. Still we are looking for ways to improve this. If you have ever done anything along these lines, we’d love to learn from your experience. How can we optimise this process?
A few requirements we have:
- No surveys. When we reach out to new contributors we are interested in a conversation with them and not necessarily interested in getting them to rate and judge each and every bit they might have interacted with. By reaching out to them, we already ask them to spare us some of their time, a long survey would likely give us more structured feedback, but less responses.
- No expensive text analysis software.
If you have any ideas how we can optimise the process, please let us know.
Also if you are interested in helping out the Developer Advisory Team, please get in touch.