Hi, We plan to migrate all existing Trac tickets [0] to the existing twisted/twisted repo from GitHub [1] We need an insider/supporter/sponsor from GitHub.com to temporarily enable access to GitHub.com Enterprise Cloud Importer . Why is that: One of the issues is that by using the public GitHub REST API, all migrated issues and comments will be visible inside GitHub as being creating the a single user (the user triggering the REST API) We are aware that the Python Software Foundation has recently completed the migration for CPython to GitHub Issues [2], using a private GitHub.com Enterprise Cloud Importer (ECI) This is a tool that is not publicly available to open source projects. Thomas wrote to GitHub support last year asking for "best practices" for GitHub migration and the answer was to use the REST API. My colleague Dan, wrote again to GitHub support giving the CPythong and LLVM migration as an example and mentioning Enterprise Cloud Importer, and the answer was that we should use the REST API as we are not an enterprise. ---- What to do if we don't have access to GitHub.com Enterprise Cloud Importer (ECI) ? I plan to wait one week to see if somehow we can manage to get access to the private import tool. We will just use the public REST API and all the issues and comments will be created/authored by a single "trac-migration" robot account. Thanks [0] https://twistedmatrix.com/trac/report/1 [1] https://github.com/twisted/twisted/ [2] https://github.com/python/cpython [3] https://github.com/psf/gh-migration/issues/13 PS.0: In the case in which you are wondering why we want to migrate from Trac. The First reason is that we don't have any volunteers having time to manage, update, maintain, upgrade ...etc, our existing Trac website. PS.1: If you want to help with the GitHub migration or help with the existing Trac website, let us know via email or join our IRC or Gitter chat. -- Adi Roiban