Thanks for that information and thanks for the service to the open source community in all these years!
Can you clarify in which way moving over to travis-ci.com will help? It seems the capacity problems are affecting travis-ci.com in a similar way? Is the queue shown at traviscistatus.com solely for travis-ci.org builds? From our own experience travis-ci.com recently has been similarly affected by high queuing times.
For many usages moving to travis-ci.com is not possible or beneficial:
- the problem that @dfawley mentioned about permissions
- travis-ci.com has big open issues with broken caches and a broken cache cleanup page (see other threads on this forum but we also experienced it ourselves), which needs manual and awkward steps to clear caches. Before I found this page we were at the point of considering to move some projects back from travis-ci.com to travis-ci.org for that reason alone
- inconsistent communication about the overall migration to travis-ci.com and what to expect and when things happen (the email with the migration deadline announcement wasn’t send to everyone, so what does that mean?)
Altogether, for bigger open source projects (which admittedly should probably have been set up on paid plans or a different kind CI in the first place), the situation points rather to a move away from Travis altogether.
Currently, it’s unclear if OS projects are going to be supported in the same way as they used to, whether the situation is going to improve any time soon, or if Travis would like to cut back on OS project support (which would be fair enough, you don’t owe us anything). It would just be nice to know what to expect 
Johannes