On Sunday, September 11, 2022 at 10:14:03 AM UTC-7 Marc Mezzarobba wrote: > Dima Pasechnik wrote: > > I've conducted few experiments with a tool to import trac sites to > > github: https://github.com/svigerske/trac-to-github, which in > > particular allows to import trac tickets as github issues; a result of > > running it on few tickets > > may be inspected > > here: > > https://github.com/dimpase/trac_to_gh/issues?q=is%3Aissue+is%3Aclosed > > How hard would it be to import issues in such a way that issues and > comments created by people with git**b accounts are correctly linked to > their accounts? This would require a way for these people to authorize > the migration script to perform specific actions in their name, or to > merge their user account with a temporary account created by the > script, or something like that. >
When the Python project transferred bugs.python.org (bpo) to GitHub Issues earlier this year, they used "mannequin" accounts to represent the old user accounts. See https://devguide.python.org/triage/github-bpo-faq/#what-on-earth-is-a-mannequin But setting this up required help by GitHub people, I think. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/bebc3ee2-0896-42d8-8ae1-4f8471c3fe33n%40googlegroups.com.
