-
Notifications
You must be signed in to change notification settings - Fork 38
process feedback from Camille B #60
Comments
Camille B is a designer and helps run a non-profit dedicated to preventing animal abuse. She might consider using Gittip to help support her non-profit. Currently they are looking for one-time "big" sponsorships, and don't have an easy way for individuals to support the effort. Design
Functionality & Placement
Overall
|
[reticketed as #61—whit537] |
@bmann Awesome interviews, thanks! The way we usually handle this kind of feedback is with a GitHub issue like "process feedback from so-and-so," which we use to further understand the feedback and then reticket new issues and/or add +1s to existing issues. The goal is to drive towards actionable issues. See here, here and here for examples. I've retitled this ticket to "process feedback from Camille B" and I've reticketed "process feedback from Alex M" as #61. |
OK. I really don't think everything can be boiled down to an issue, but I guess we'll roll with what we have for now. I don't think feedback can be "processed" individually. In fact, it's highly dangerous in overfocusing on one person, vs. looking for themes and finding 10 or 20 or 30 people that all want the same thing / react the same way. So perhaps just list it as feedback / interview / whatever and leave it at that. |
That's exactly what ends up happening with this method. So, for example, Camille mentions that she "would like the option to give funds through a bank account." I've added a +1 for her to gratipay/gratipay.com#777. Some things she mentions are old tickets, some should be new tickets, some aren't things we're going to worry about ("not a fan of the logo").
Boiling everything down to an issue means we only care about action items. If we can't act on something, then ... what are we supposed to do about it? |
👍 to the overall gathering of the surveys. Awesome stuff. I'm inclined to agree with @whit537 that the "processing" approach has worked well for us, with +1's, new issues, etc. Just because an issue is created doesn't necessarily mean it's any sort of high priority, but it's nice to get the "ask" down in one place. Many feedback items relate to outstanding issues that have history, and issues work great for cross-referencing by those contributors with more historical context, for the later benefit of those with less. I found issue cross-referencing so useful when I first started :) |
Closing as outdated. A lot has happened since we collected this feedback. |
I have a couple of pieces of (written) feedback from people. I am going to stick them in this issue for now, but something like using the Github wiki would be a much easier place.
[was "Where to put feedback?"]
The text was updated successfully, but these errors were encountered: