<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span lang=EN-AU>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).<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-AU>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.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-AU>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.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-AU>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.</span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Top-posted from my Windows 10 phone</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:levkivskyi@gmail.com">Ivan Levkivskyi</a><br><b>Sent: </b>Friday, June 1, 2018 18:05<br><b>To: </b><a href="mailto:barry@python.org">Barry Warsaw</a><br><b>Cc: </b><a href="mailto:python-committers@python.org">python-committers</a><br><b>Subject: </b>Re: [python-committers] Comments on moving issues to GitHub</p></div><p class=MsoNormal><o:p> </o:p></p><div><div><div><p class=MsoNormal>On 1 June 2018 at 20:29, Barry Warsaw <<a href="mailto:barry@python.org" target="_blank">barry@python.org</a>> wrote:</p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal style='margin-bottom:12.0pt'>On Jun 1, 2018, at 16:54, Antoine Pitrou <<a href="mailto:antoine@python.org">antoine@python.org</a>> wrote:<br>> <br>> I wonder if other hosted services, such as Gitlab, offer a more<br>> sophisticated issue tracker.</p></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Note that GitHub (and I think GitLab too) provides two additional ways to categorise issues: project boards, and milestones.</p></div><div><p class=MsoNormal>I think together with labels this may simulate current b.p.o. structure to certain extent. For example (approximately):</p></div><div><p class=MsoNormal>* We can have milestones for releases (including past releases)</p></div><div><p class=MsoNormal>* We can have "project boards" (slightly abusing this feature): new, triaged, PR review</p></div><div><p class=MsoNormal>* Labels can be grouped using name prefix and color, for example (we have similar structure in mypy):</p></div><div><p class=MsoNormal> - priority-low</p></div><div><p class=MsoNormal> - priority-normal</p></div><div><p class=MsoNormal> - priority-etc...</p></div><div><p class=MsoNormal> - kind-bug</p></div><div><p class=MsoNormal> - kind-docs</p></div><div><p class=MsoNormal> - kind-feature</p></div><div><p class=MsoNormal> - topic-asincio</p></div><div><p class=MsoNormal> - topic-etc..</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>This is still quite limited, but together with bots this can practically replace current categorisation.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>--</p></div><div><p class=MsoNormal>Ivan</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>