Re: [matplotlib-devel] git migration this weekend

[Eric F. <ef...@ha...>]

On 02/26/2011 10:54 AM, Darren Dale wrote:
> On Sat, Feb 26, 2011 at 3:52 PM, Darren Dale<dsd...@gm...>  wrote:
>> On Sat, Feb 26, 2011 at 2:52 PM, Eric Firing<ef...@ha...>  wrote:
>>> On 02/26/2011 09:26 AM, Darren Dale wrote:
>>>> On Wed, Feb 16, 2011 at 2:19 PM, Eric Firing<ef...@ha...>    wrote:
>>>>> On 02/16/2011 08:38 AM, Darren Dale wrote:
>>>>>> On Wed, Feb 16, 2011 at 12:39 PM, Fernando Perez<fpe...@gm...>      wrote:
>>>>>>> are you guys planning on transfering the old bugs to github?
>>>>>>
>>>>>> Probably at some point.
>>>>>>
>>>>>>> As I
>>>>>>> mentioned, I have code lying around for the upload (and to download
>>>>>>> from launchpad, but that's irrelevant here).  I'm going to be mosly
>>>>>>> offline til Monday (conference trip), but if someone pings me on my
>>>>>>> Berkeley email address, which I monitor even while traveling, I'll be
>>>>>>> happy to help out.
>>>>>>
>>>>>> Thanks, that would be very helpful. I'll follow up once I figure out
>>>>>> how to extract the information from sourceforge.
>>>>>
>>>>> Darren,
>>>>>
>>>>> Just a heads-up on that: In November the tracker was heavily spammed.
>>>>> Recently I marked a few hundred items with the "delete" disposition, but
>>>>> I don't think that actually gets rid of them.  If it doesn't, then maybe
>>>>> they can be filtered out during the transfer.
>>>>
>>>> We have some additional spam that needs to be deleted. How did you do
>>>> it? When I try to delete several at once (mass change), I get an error
>>>> message: "XSRF Attempt Detected!"
>>>>
>>>
>>> I made the tracker display the maximum number of entries per page, then
>>> clicked "check all", then "mass update" with "delete", and it marked
>>> them as "deleted"--but they never get deleted.  They are still there,
>>> but marked "deleted". It sounds like that is the same as what you tried,
>>> so I don't know why you are getting that error message.
>>>
>>> Which tracker category is showing the new spam?
>>
>> The Feature Requests. I was not able to mark the spam as deleted, but
>> I filtered it out in the conversion.
>
> Let me try again:
>
> The tracker export xml file and conversion script are up at
> https://github.com/darrendale/mpl-issues , and the issues can be
> previewed at https://github.com/darrendale/mpl-issues/issues . Devs,
> please have a
> look. I only imported the open issues, including bugs, patches,
> feature requests and support requests. If we decide to use the github
> tracker, we can tell sourceforge we have relocated the project, and
> the project will remain intact and archived. I don't know if that
> would mean that we can no longer host the homepage at sourceforge.

The submitter info is lost?
And when it was originally submitted?
If yes to either, then I think that we should not transfer these from 
sourceforge, but deal with them there.
Overall, the tracking interface on github looks so bad that I can't see 
why we would want to move.  Sourceforge is slow, but at least the 
tracker has the right sort of functionality: the ability to scan a lot 
of info on one screen, the ability to categorize, attach files, assign, 
etc.  Maybe some of this is available but not evident in the github 
tracker, but what I see is not encouraging.

Mpl historically has not done well in using the tracker.  I hope that 
eventually we can transition to a tool that will help us do better, not 
worse.

Eric