team-compass
team-compass copied to clipboard
Feb 2020 user survey
This issue is to track follow-up from the user survey.
The first thing we should do is decide when to close they survey. I don't remember how we decided when to close it last time. I'd propose we pick some (somewhat arbitrary) condition that we haven't yet reached and then close when we have reached it.
Another idea to discuss: I was thinking we should write a short blog post that summarises the feedback we got. In particular from the "one thing you'd improve" section. I think it would be good to just present the results from the survey without responding to them or explaining why it is hard to do some of the things people ask for. For me te goal would be to share what kind of feedback we got, show that it is diverse (different people want different stuff). Then at a later stage we can follow up with a post (eg about persistence) that explains what we have done, what we are thinking right now, etc. What do you think?
Maybe a good arbitrary point to close it is the next team meeting?
Relating to #256, the first language-specific meeting I plan to attend is at the end of May. So it could even be done in the April team meeting?
I think it's a great idea to have a summary blog post 👍
I'd vote to close the poll "soon", days or weeks from now. What do others think?
@betatim wrote
For me the goal would be to share what kind of feedback we got, show that it is diverse (different people want different stuff).
Looking forward to seeing the responses ;)
Link to the poll https://docs.google.com/forms/d/1mY4rE6PgvpbLlw9bK61Bp4-XdPNqAIBsT_Ly55GYDvE/edit. Should let you look at the results and edit (I think). Sorry for not posting it more prominently, I thought I had already done that :(
cc @choldgraf
thanks!
I'm still impressed by the diversity of use-cases that we have!
cc @fedenanni RE: this comment https://github.com/jupyterhub/team-compass/issues/256#issuecomment-611510982