[python-committers] Comments on moving issues to GitHub

Steve Dower steve.dower at python.org
Sat Jun 2 10:30:24 EDT 2018

I think boards have improved since I last used them, but when I tried they added nothing but overhead. Possibly useful for planning, if we had someone who was responsible for that (maybe individual planning? But then you can’t really expect contributors to keep it up to date for you).

Milestones are one-per-issue, and get rolled up in a way that is most useful for planning rather than search or review. I use these all the time on work projects.

A good set of tags (which unfortunately are shared with the set of tags you can put on a PR) and some automation to auto-subscribe the core devs associated with that tag is a bare minimum, as far as I’m concerned. It would be nice if issue search supported the OR operator as well, but it can only do AND.

I’m far from convinced that GitHub issues will work well for an active team as large as ours with as little coordination as we use. It doesn’t work well for the “bucket of bugs” I keep open on one of my work projects, even though the team is smaller, and our tracker is almost entirely a bucket of bugs.

Top-posted from my Windows 10 phone

From: Ivan Levkivskyi
Sent: Friday, June 1, 2018 18:05
To: Barry Warsaw
Cc: python-committers
Subject: Re: [python-committers] Comments on moving issues to GitHub

On 1 June 2018 at 20:29, Barry Warsaw <barry at python.org> wrote:
On Jun 1, 2018, at 16:54, Antoine Pitrou <antoine at python.org> wrote:
> I wonder if other hosted services, such as Gitlab, offer a more
> sophisticated issue tracker.

Note that GitHub (and I think GitLab too) provides two additional ways to categorise issues: project boards, and milestones.
I think together with labels this may simulate current b.p.o. structure to certain extent. For example (approximately):
* We can have milestones for releases (including past releases)
* We can have "project boards" (slightly abusing this feature): new, triaged, PR review
* Labels can be grouped using name prefix and color, for example (we have similar structure in mypy):
  - priority-low
  - priority-normal
  - priority-etc...
  - kind-bug
  - kind-docs
  - kind-feature
  - topic-asincio
  - topic-etc..

This is still quite limited, but together with bots this can practically replace current categorisation.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20180602/8813f4e5/attachment.html>

More information about the python-committers mailing list