sort out migration from sourceforge.net

[pexpect]

sort out migration from sourceforge.net

[takluyver]

Hi Sorin! You're 'intersol' on Sourceforge, right?

After a bug was filed yesterday, I've worked out how to close off the SF bug trackers so people can't file new reports on them. It would be good to get the issues that are open there migrated to Github or closed, but many of them are ancient, and it may not be easy to work out if they're still relevant. If you've got time to help with triaging them, that would certainly be welcome.

[ssbarnea]

Yes my account on SF is "intersol". I observed that there is a python migration tool that we could you to import. If we have the source code with history and bugs migrated we can even request SF.net to remove the project, as this would only help people find the right location easier.

https://sourceforge.net/apps/trac/sourceforge/wiki/Removing%20a%20project

[takluyver]

I'm inclined to leave the Sourceforge page in existence, pointing people who still try to go there in the right direction.

• pexpect.sourceforge.net redirects to the docs on RTD
• https://sourceforge.net/projects/pexpect/ has prominent links to Github and RTD
• New tickets can no longer be filed (except by project admins, I think), so this shouldn't confuse people.

I'm tempted to delete the 'Code' tool so people don't think the SVN repo is the canonical location for Pexpect development. I don't know how to check that all the history was faithfully preserved before I do that, though.

[jquast]

Closing, nobody has so far reported confusion about having moved from sourceforge. The banner, "As of 2014-06-03, this project may now be found at https://github.com/pexpect/pexpect." seems to be very successful so far in driving issue reporters and code hunters here.