On Saturday, 17 September 2022 at 17:55:10 UTC-7 Matthias Koeppe wrote: > > The conversion of the Trac tickets to GitHub Issues/PRs only works in one > shot. Incrementally syncing updates from Trac to existing issues is not > possible. >
Migration *to* GH is one thing, but as has been pointed out, we should have an exit strategy as well, or at least an idea of a roadmap to move from github to elsewhere. The code itself is trivial to move: it's a git repo. However, as has been shown in the past, the discussions (now in tickets on trac, but if moved in issues and PRs) can sometimes be of immense value as well. I suppose that if moving from GH to GL is as trivial as claimed before, GH must have a way of exporting issues and PRs. Would someone be able to give an informed assessment or a feasibility study of extracting issues and PRs from GH? How searchable are they and how do cross-links survive an extraction (also important for trac-to-GH)? Presently, trac is fairly searchable due to its own search functions plus its general indexing by google's search engine. Hopefully we'd have something at least matching that for GH. Perhaps part of our setup should also be that we "backup" this part of our github setup: githubs own infrastructure is of course excellently resilient against technological problems but a new failure mode is introduced due to their governance and policy: in the extremely unlikely event that sagemath on GH would get "locked" due to a misunderstanding (or malice?) we might not be at their mercy for extracting our valuable history. -- 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/0e2df7b4-3dca-4b1c-b93c-2e893673b687n%40googlegroups.com.
