-
-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JupyterLab 3.0 release survey #107
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I approve of this survey even without the addition of my suggestions. Thank you all for your hard work pushing this survey through all our rounds of review!
At this point, we have 7 responses. I assume it's people on this thread as it hasn't been shared. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@willingc You're right; question 7 was brutal, but I still don't want to go against the community in deleting or drastically changing it, so I am simplifying the response choices about meeting expectations to this: I'll manually port over the sentiment of the initial 7 responses when making the raw data available. |
Co-authored-by: Isabela Presedo-Floyd <[email protected]>
Co-authored-by: Isabela Presedo-Floyd <[email protected]>
Thank you all for helping with this, I have synced the remaining few suggestions that were applied to the survey and this is now ready to merge. |
Thank you for all the hard work everybody. Hopefully we can learn from this process to make the next user survey we compose come together more smoothly for a future release. |
Yes, thank you everyone for participating and getting this ready. I am
excited to see what we can learn from this. Great work!
…On Fri, Nov 20, 2020 at 8:48 AM Afshin Taylor Darian < ***@***.***> wrote:
Thank you for all the hard work everybody. Hopefully we can learn from
this process to make the next user survey we compose come together more
smoothly for a future release.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#107 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAGXUFZA7H3G4W4SWQSF4TSQ2MXHANCNFSM4TJR63ZQ>
.
--
Brian E. Granger
Principal Technical Program Manager, AWS AI Platform ([email protected])
On Leave - Professor of Physics and Data Science, Cal Poly
@ellisonbg on GitHub
|
Based on the discussion initiated at the JupyterLab vision for the next few years a few JupyterLab community members put together a survey that would ask related questions based on items raised on that thread.
The idea is to leverage the announcement of the JupyterLab 3.0 release to amplify the reach for the survey. We have also discussed the possibility to add links to
binder
and other projects with high visibility to help with the spread of the survey.The survey raw data will then be made available for the community.
Fixes #104
Notes: