Add open issues analysis

[fcollonval]

Following the dev meeting of July 7th, here is a notebook that analyze the JupyterLab opened issues.

Xref: #117 (comment)

The notebook can be visualized directly in GitHub: https://github.com/jupyterlab/team-compass/blob/ft/issues-insights/docs/insights/JupyterLab_issues.ipynb

[welcome]

Thanks for submitting your first pull request! You are awesome! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please make sure you followed the pull request template, as this will help us review your contribution more quickly.

You can meet the other Jovyans by joining our Discourse forum. There is also a intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

[telamonian]

hmm, interesting. Apparently people were bringing up a lot of especially difficult issues at the start of 2018, for some reason

[krassowski]

Thanks @fcollonval. I will also take a stab at the text analysis during the weekend (if there won't be another heatwave...).

hmm, interesting. Apparently people were bringing up a lot of especially difficult issues at the start of 2018, for some reason

Would be good to normalize by total number of issues opened at given time for that conclusion I think? There might have been a spike in total number of issues after https://blog.jupyter.org/jupyterlab-is-ready-for-users-5a6f039b8906 announcement.

[fcollonval]

There might have been a spike in total number of issues after https://blog.jupyter.org/jupyterlab-is-ready-for-users-5a6f039b8906 announcement.

This sounds like a plausible cause as the peak is on the approximate second month. But you are correct, some normalization would make sense (and probably stricter construction of bin per month).

[telamonian]

Would be good to normalize by total number of issues opened at given time for that conclusion I think? There might have been a spike in total number of issues after https://blog.jupyter.org/jupyterlab-is-ready-for-users-5a6f039b8906 announcement.

Yeah, sure, but doesn't a sudden plague of vexatious users sound much funnier?

+1 for adding some plots with (issues still open/total count of issues opened) normalized bins. That would help to sort out some of these possible hypotheses. Tho for the 2018 spike historical contingency does seem the likeliest explanation, given the preceding blogpost

[krassowski]

Is it possible to get reactions (:+1:, :-1: etc) stats with this API? I am thinking like weighting n-grams by those...

[fcollonval]

Is it possible to get reactions (+1, -1 etc) stats with this API? I am thinking like weighting n-grams by those...

This is possible although it will require more API request (see https://ghapi.fast.ai/fullapi.html#reactions and https://docs.github.com/en/rest/reference/reactions#list-reactions-for-an-issue). This means we may hit the GitHub anonymous request quota (I try to avoid bringing authentication for easiness).