Quantcast

The GitHub labels

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

The GitHub labels

Nelle Varoquaux
Hi team,

We've been discussing at several occasions of cleaning up our GitHub
labels, and merging some. In order to guide the discussion of which
labels to keep and to move, I've analysed a bit what where the labels
we were using. Attached is a plot of the number of issues (including
PRs) open and closed for each labels.
Maybe we have too many labels? Most of them don't seem actively used.
For example, py3k seem to be used 4 times, only on closed tickets/PR.

I've done a similar analysis on scikit-image, scikit-learn and
ipython. Some labels seem to be consistently used quite highly across
all projects: the 3 difficulty levels, bug, ENH, DOC.

I'm playing a bit with the github API this afternoon, so if any other
statistics is useful, just let me know.

Cheers,
N

------------------------------------------------------------------------------
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive.
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik
_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

matplotlib_labels.png (88K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [matplotlib-devel] The GitHub labels

Paul Hobson-2
Nelle,

Thanks for pulling this together. You sent it to this old source forge list and not the new python.org list, so I've fixed that with this reply.

Honestly, the graph makes to problems not seem as bad as I thought it was. I feel like most of the low-count tags like the MEPs and backends should stay. But certainly things like "low-hanging" fruit and "Difficulty: Easy" could be merged.

-paul

On Sat, Oct 29, 2016 at 2:45 PM, Nelle Varoquaux <[hidden email]> wrote:
Hi team,

We've been discussing at several occasions of cleaning up our GitHub
labels, and merging some. In order to guide the discussion of which
labels to keep and to move, I've analysed a bit what where the labels
we were using. Attached is a plot of the number of issues (including
PRs) open and closed for each labels.
Maybe we have too many labels? Most of them don't seem actively used.
For example, py3k seem to be used 4 times, only on closed tickets/PR.

I've done a similar analysis on scikit-image, scikit-learn and
ipython. Some labels seem to be consistently used quite highly across
all projects: the 3 difficulty levels, bug, ENH, DOC.

I'm playing a bit with the github API this afternoon, so if any other
statistics is useful, just let me know.

Cheers,
N

------------------------------------------------------------------------------
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive.
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik
_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel



_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/matplotlib-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[Matplotlib-devel] [matplotlib-devel] The GitHub labels

tcaswell
In reply to this post by Nelle Varoquaux
Forward of Nelle's orginal email to the python.org list (which should have the graph Paul is talking about attached).

Tom

---------- Forwarded message ---------
From: Nelle Varoquaux <[hidden email]>
Date: Sat, Oct 29, 2016 at 5:46 PM
Subject: [matplotlib-devel] The GitHub labels
To: [hidden email] <[hidden email]>


Hi team,

We've been discussing at several occasions of cleaning up our GitHub
labels, and merging some. In order to guide the discussion of which
labels to keep and to move, I've analysed a bit what where the labels
we were using. Attached is a plot of the number of issues (including
PRs) open and closed for each labels.
Maybe we have too many labels? Most of them don't seem actively used.
For example, py3k seem to be used 4 times, only on closed tickets/PR.

I've done a similar analysis on scikit-image, scikit-learn and
ipython. Some labels seem to be consistently used quite highly across
all projects: the 3 difficulty levels, bug, ENH, DOC.

I'm playing a bit with the github API this afternoon, so if any other
statistics is useful, just let me know.

Cheers,
N
------------------------------------------------------------------------------
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive.
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/matplotlib-devel

matplotlib_labels.png (88K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[Matplotlib-devel] Fwd: [matplotlib-devel] The GitHub labels

Paul Hobson-2
In reply to this post by Nelle Varoquaux
Here's Nelle's email re: the current usage of GH labels.


---------- Forwarded message ----------
From: Nelle Varoquaux <[hidden email]>
Date: Sat, Oct 29, 2016 at 2:45 PM
Subject: [matplotlib-devel] The GitHub labels
To: "[hidden email]" <[hidden email]>


Hi team,

We've been discussing at several occasions of cleaning up our GitHub
labels, and merging some. In order to guide the discussion of which
labels to keep and to move, I've analysed a bit what where the labels
we were using. Attached is a plot of the number of issues (including
PRs) open and closed for each labels.
Maybe we have too many labels? Most of them don't seem actively used.
For example, py3k seem to be used 4 times, only on closed tickets/PR.

I've done a similar analysis on scikit-image, scikit-learn and
ipython. Some labels seem to be consistently used quite highly across
all projects: the 3 difficulty levels, bug, ENH, DOC.

I'm playing a bit with the github API this afternoon, so if any other
statistics is useful, just let me know.

Cheers,
N

------------------------------------------------------------------------------
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive.
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik
_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel



_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/matplotlib-devel

matplotlib_labels.png (88K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Fwd: [matplotlib-devel] The GitHub labels

Elliott Sales de Andrade
Hi Nelle,

Can you a) sort by count instead of alphabetically and maybe b) split by >100 vs <100? About three or four labels are drowning out the rest and it's hard to say if any of the small ones are just one or two, or just relatively small.

On 1 November 2016 at 13:11, Paul Hobson <[hidden email]> wrote:
Here's Nelle's email re: the current usage of GH labels.


---------- Forwarded message ----------
From: Nelle Varoquaux <[hidden email]>
Date: Sat, Oct 29, 2016 at 2:45 PM
Subject: [matplotlib-devel] The GitHub labels
To: "[hidden email]" <[hidden email]>


Hi team,

We've been discussing at several occasions of cleaning up our GitHub
labels, and merging some. In order to guide the discussion of which
labels to keep and to move, I've analysed a bit what where the labels
we were using. Attached is a plot of the number of issues (including
PRs) open and closed for each labels.
Maybe we have too many labels? Most of them don't seem actively used.
For example, py3k seem to be used 4 times, only on closed tickets/PR.

I've done a similar analysis on scikit-image, scikit-learn and
ipython. Some labels seem to be consistently used quite highly across
all projects: the 3 difficulty levels, bug, ENH, DOC.

I'm playing a bit with the github API this afternoon, so if any other
statistics is useful, just let me know.

Cheers,
N

------------------------------------------------------------------------------
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive.
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik
_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel



_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/matplotlib-devel




--
Elliott

_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/matplotlib-devel
Loading...