It's really unclear what's going on here – Github is saying that you have to migrate, but Travis is saying that you can't migrate, and there haven't been any updates for months now. This isn't specific to scipy; every project using Travis is in the same position. I can only assume there are people at both companies holding panicked conference calls. I don't think there's anything we can do except wait for Github/Travis to get their act together and tell us what's happening. -n

If it helps, I just tried the follow the docs in the first message in this thread for PyData/Sparse, and it wouldn’t let me activate the repo on .com, saying it was already active on .org

I had the same problem and if you don't want the build history (which probably you don't care) you can email them. I did and they replied as below. So maybe someone with higher priviledges can start the discussion by emailing them.

Hi Ilhan,

Thanks for wriiting in!

I have activated our beta migration feature for your personal account. Please let me know if this is something you'd also like to have activated in one or more of your organizations and I'll set it up for your team.

To help you start migrating your open source repositories to travis-ci.com, we have created this guide https://docs.travis-ci.com/user/open-source-repository-migration/ that contains the instructions to transfer a project as well as some other details we thought might be useful, including what does it look like to work with a repository once it's been migrated.

We're here for any questions or comments you might have. We'll continue shipping improvements to the beta, and if you find something that can help us improve, we’d love to hear what you think.

Thank you, and happy building! Carla

So apparently there is a beta process going on already.

I can only assume there are people at both companies holding panicked conference calls. I don't think there's anything we can do except wait for Github/Travis to get their act together and tell us what's happening

I would use a slightly different tone :) but I agree in general. We are kind of taking their availability for granted however it is nice that we can still use these tools for free hence I would grant some screw-up buffer to them. Maybe it's the Microsoft effect or other CEO issues; who knows. On Mon, Dec 24, 2018 at 11:24 AM Hameer Abbasi <einstein.edison@gmail.com> wrote:

If it helps, I just tried the follow the docs in the first message in this thread for PyData/Sparse, and it wouldn’t let me activate the repo on .com, saying it was already active on .org. You can see the discussion here: https://github.com/pydata/sparse/issues/224

Best Regards, Hameer Abbasi

On Sunday, Dec 23, 2018 at 11:47 PM, Nathaniel Smith <njs@pobox.com> wrote: It's really unclear what's going on here – Github is saying that you have to migrate, but Travis is saying that you can't migrate, and there haven't been any updates for months now. This isn't specific to scipy; every project using Travis is in the same position. I can only assume there are people at both companies holding panicked conference calls. I don't think there's anything we can do except wait for Github/Travis to get their act together and tell us what's happening.

-n _______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev

_______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev