Re: [core-workflow] GSoC idea: bug.python.org improvements

2015-03-22 Thread Nick Coghlan
On 22 March 2015 at 14:11, Ezio Melotti wrote: > On Sat, Mar 21, 2015 at 9:33 PM, R. David Murray > wrote: >> On Sat, 21 Mar 2015 23:13:13 +1000, Nick Coghlan wrote: >>> I don't think we've discussed it anywhere yet (unless I mentioned it >>> to Ezio on IRC), but there are some issues around de

Re: [core-workflow] GSoC idea: bug.python.org improvements

2015-03-22 Thread Jørn Lomax
On 22.03.2015 08:50, Nick Coghlan wrote: On 22 March 2015 at 14:11, Ezio Melotti wrote: On Sat, Mar 21, 2015 at 9:33 PM, R. David Murray wrote: On Sat, 21 Mar 2015 23:13:13 +1000, Nick Coghlan wrote: I don't think we've discussed it anywhere yet (unless I mentioned it to Ezio on IRC), but

Re: [core-workflow] GSoC idea: bug.python.org improvements

2015-03-22 Thread Ezio Melotti
On Sun, Mar 22, 2015 at 2:02 PM, Jørn Lomax wrote: > > So as a student, if I'm writing a proposal to the project I should just > mark it as bug tracker improvements and fixes? Yes. > It just seem a little hard to > point to very specific goals to complete, and the project would gain more > goal

Re: [core-workflow] GSoC idea: bug.python.org improvements

2015-03-22 Thread Ezio Melotti
On Sun, Mar 22, 2015 at 9:50 AM, Nick Coghlan wrote: > On 22 March 2015 at 14:11, Ezio Melotti wrote: >> On Sat, Mar 21, 2015 at 9:33 PM, R. David Murray >> wrote: >>> On Sat, 21 Mar 2015 23:13:13 +1000, Nick Coghlan wrote: I don't think we've discussed it anywhere yet (unless I mentioned