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

On 3 June 2018 at 17:00, Nick Coghlan wrote: > I'll also email Maciej & EW Durbin ([1]) to see if they've had a chance to > discuss the rehosting plans for bugs.python.org yet. > The status update here is that Maciej has been bringing Ernest up to speed on the preparatory work that has already b

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

On 3 June 2018 at 12:49, Brett Cannon wrote: > > On Sat, 2 Jun 2018 at 14:58 Ezio Melotti wrote: > > Even if the volunteers don't materialize (and I dematerialize), we >> still have to determine if the cost of keep using b.p.o as is, is >> greater than the cost of moving everything to a new syst

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

On Sat, 2 Jun 2018 at 14:58 Ezio Melotti wrote: > Hi, > > On Sat, Jun 2, 2018 at 10:26 PM, Brett Cannon wrote: > > > > > > On Sat, 2 Jun 2018 at 12:47 Mariatta Wijaya > > wrote: > >> > >> [SNIP] > >> > >>> 2. Better support for core developers in the tracker. > >> > >> > >> Not sure what you me

[python-committers] Comments on moving issues to GitHub

Reading the comments in the thread and having used Github issues myself for a few years now, I find the idea of moving from a dedicated issue tracker we can easily customize to our needs (or hire someone to do so via the PSF) to a simplistic tracker add-on, which Github issues is, not a very promis

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

Hi, On Sat, Jun 2, 2018 at 10:26 PM, Brett Cannon wrote: > > > On Sat, 2 Jun 2018 at 12:47 Mariatta Wijaya > wrote: >> >> [SNIP] >> >>> 2. Better support for core developers in the tracker. >> >> >> Not sure what you mean by "support"? There are only two maintainers of the >> bug tracker, they b

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

Would it be possible to get a database(s) download of all of the b.p.o. data (redacting privacy information if needed)? I would like to work on a proof of concept using the scientific python stack, particularly Pandas, to see if we can do a GitHub/GitLab (pick your favorite) for all new issues

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

On Sat, 2 Jun 2018 at 12:47 Mariatta Wijaya wrote: > [SNIP] > > 2. Better support for core developers in the tracker. > > > Not sure what you mean by "support"? There are only two maintainers of the > bug tracker, they both are also Python core developers: Brett and Ezio. My > personal opinion is

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

> > "Old and languishing issues should just be closed / ignored" > I disagree with doing this blindly, and I would be mightily annoyed if > someone did so with IDLE issues and hide valuable ideas and code. Since you are IDLE's maintainer, I'll also be annoyed if other people except yourself (or o

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

-committers Subject: Re: [python-committers] Comments on moving issues to GitHub 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 GitH

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

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

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

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

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

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

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

On 05/20/2018 10:19 AM, Nathaniel Smith wrote: On Sun, May 20, 2018, 03:18 Antoine Pitrou > wrote: Le 19/05/2018 à 02:10, Victor Stinner a écrit : > Hi, > > I failed to get the microphone after Mariatta's secret talk about > moving Python issues

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

On May 21, 2018, at 03:24, Nick Coghlan wrote: > Right, one of the outcomes of the discussion at the Summit was that any > proposal to migrate to a different issue tracker would need to present a > clear statement of the *problems intended to be solved*, such that the folks > that would prefer

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

On 21 May 2018 at 05:03, Brett Cannon wrote: > > > On Sun, 20 May 2018 at 10:43 Barry Warsaw wrote: > >> On May 20, 2018, at 10:19, Nathaniel Smith wrote: >> > >> > IIRC, the general reaction was that it was definitely worth exploring, >> but that it would be a lot of work and require solutions

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

On Sun, 20 May 2018 at 10:43 Barry Warsaw wrote: > On May 20, 2018, at 10:19, Nathaniel Smith wrote: > > > > IIRC, the general reaction was that it was definitely worth exploring, > but that it would be a lot of work and require solutions to a lot of > problems to make sure people's workflows we

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

On May 20, 2018, at 10:19, Nathaniel Smith wrote: > > IIRC, the general reaction was that it was definitely worth exploring, but > that it would be a lot of work and require solutions to a lot of problems to > make sure people's workflows weren't too impacted, so we'd need a much more > detail

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

On Sun, May 20, 2018, 03:18 Antoine Pitrou wrote: > > Le 19/05/2018 à 02:10, Victor Stinner a écrit : > > Hi, > > > > I failed to get the microphone after Mariatta's secret talk about > > moving Python issues from bugs.python.org (Roundup) to GitHub. > > A "secret talk"? What is that? > She gave

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

On Sun, May 20, 2018 at 10:56:21AM +0200, Antoine Pitrou wrote: > If that's on the table, it seems to me that categorization, sorting and > filtering on GitHub issues is rather poor, while the basic UI experience > (editing messages, etc.) is better. Also, I think customization (e.g. > of the defa

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

Le 19/05/2018 à 02:10, Victor Stinner a écrit : > Hi, > > I failed to get the microphone after Mariatta's secret talk about > moving Python issues from bugs.python.org (Roundup) to GitHub. A "secret talk"? What is that? > I don't have a strong opinion about moving issues to GitHub. If that's o

[python-committers] Comments on moving issues to GitHub

Hi, I failed to get the microphone after Mariatta's secret talk about moving Python issues from bugs.python.org (Roundup) to GitHub. I just wanted to add that it's common (at least once per month) that someone comes to #python-dev to report that they cannot connect to bugs.python.org (the authent