Re: [python-committers] Comments on moving issues to GitHub

2018-06-01 Thread Terry Reedy
On 6/1/2018 7:07 PM, Mariatta Wijaya wrote: Yup, the "mystery" was just for fun 😛 There is no secret. I've been thinking that we should start using GitHub issues instead of the b.p.o. I realized not everyone was able to get to the language summit, and I fully intended to update python-committ

Re: [python-committers] Comments on moving issues to GitHub

2018-06-01 Thread Ivan Levkivskyi
On 1 June 2018 at 20:29, Barry Warsaw wrote: > On Jun 1, 2018, at 16:54, Antoine Pitrou 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:

Re: [python-committers] Comments on moving issues to GitHub

2018-06-01 Thread Barry Warsaw
On Jun 1, 2018, at 16:54, Antoine Pitrou wrote: > > I wonder if other hosted services, such as Gitlab, offer a more > sophisticated issue tracker. Not really. Mailman has a little less than 200 open issues, but they are basically categorized in the same way as GitHub, i.e. via labels. https:/

Re: [python-committers] Comments on moving issues to GitHub

2018-06-01 Thread Antoine Pitrou
Hi Mariatta, Le 02/06/2018 à 01:07, Mariatta Wijaya a écrit : > > For those who missed it, some resources: > > 1. My language summit slides > (https://speakerdeck.com/mariatta/mariattas-python-language-summit-2018-presentation) > There are 3 bonus slides at the end which I did not get to cover,

Re: [python-committers] Comments on moving issues to GitHub

2018-06-01 Thread Mariatta Wijaya
Yup, the "mystery" was just for fun 😛 There is no secret. I've been thinking that we should start using GitHub issues instead of the b.p.o. I realized not everyone was able to get to the language summit, and I fully intended to update python-committers with this idea. I just haven't been reading t