JupyterLab 3.0 release survey

[lresende]

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:

• There are some questions that, in markdown, the UX seem very undesirable, particularly on tabled questions with multiple options. Please use the survey link to see the final UX based on the used tool.

[lresende]

It seems that I can only select 15 reviewers, so I am pinging the team here for awareness @jupyterlab/committers

[ghost]

Yes! Absolutely! Good catch.

On Sun, Nov 8, 2020 at 3:12 PM Carol Willing notifications@github.com wrote:

@willingc approved this pull request.

@LayneSadler https://github.com/LayneSadler I really like the changes that you made. It looks like you have addressed all feedback. Thanks!

One thing I forgot earlier: We should add "Julia" to the list of languages used. Sorry, I overlooked earlier.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jupyterlab/team-compass/pull/107#pullrequestreview-525840799, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD5BNPHOZZ6NNFQI4VC3H5LSO33RDANCNFSM4TJR63ZQ .

--

Layne Sadlerlayne.sadler@gmail.com linkedin.com/in/laynesadler 978.833.4190

[lresende]

Thank you @LayneSadler for keeping close eye and updating the survey. I have also sync the survey and pr.

[ghost]

At this point, we have 7 responses. I assume it's people on this thread as it hasn't been shared.

[ghost]

@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.

[lresende]

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.

[afshin]

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.

[ellisonbg]

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 < notifications@github.com> 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 https://github.com/jupyterlab/team-compass/pull/107#issuecomment-731280021, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAGXUFZA7H3G4W4SWQSF4TSQ2MXHANCNFSM4TJR63ZQ .

-- Brian E. Granger

Principal Technical Program Manager, AWS AI Platform (brgrange@amazon.com) On Leave - Professor of Physics and Data Science, Cal Poly @ellisonbg on GitHub