Yes, this is the intended presentation in the migration archive format, see https://github.github.com/enterprise-migrations/#/./2.1-export-archive-format. The ticket descriptions and the comments are shown in the final format. The metadata are presented as JSON data.
What should be checked now is that (1) descriptions/comments have been correctly transformed (from the Trac wiki markup to Github-flavored markdown) and (2) Trac attributes and their changes have been correctly transformed into metadata for issues, issue comments, and issue events. After importing this migration archive in a GitHub server (first a temporary GH Enterprise Server, later the final import in GitHub.com), it will be visually appealing. On Tuesday, December 27, 2022 at 5:24:59 PM UTC-8 dmo...@deductivepress.ca wrote: > When I click on any of the converted files in my browser, each issue > includes a block of raw json code. (Screenshot of a typical issue is > attached.) Is it supposed to be like that? Or I am supposed to be opening > the file some other way (on MacOS)? It would be much better to see the > information in a visually appealing format. > > > On Monday, December 26, 2022 at 8:34:58 PM UTC-7 Matthias Koeppe wrote: > >> I would propose that we target Feb 1, 2023 as the day on which we switch >> from Trac to GitHub. >> This gives us more than 1 month for inspecting the converted issues and >> fine-tuning the conversion. >> >> I've updated https://trac.sagemath.org/ticket/30363 and >> https://github.com/sagemath/sage/wiki/migration-from-trac-to-Git**b >> >> On Sunday, December 25, 2022 at 2:08:34 PM UTC-8 Matthias Koeppe wrote: >> >>> All 35000 converted issues are now available for inspection in >>> subdirectories like Issues-33xxx >>> <https://github.com/sagemath/trac_to_gh/tree/main/Issues-33xxx> in >>> https://github.com/sagemath/trac_to_gh >>> >>> On Sunday, December 25, 2022 at 3:36:23 AM UTC-8 Kwankyu Lee wrote: >>> >>>> The migration script accesses the Trac server via XMLRPC and does not >>>>> need privileged access. The first conversion of our 35000 tickets takes >>>>> about 8 hours. The migration script keeps a disk cache for the Trac data, >>>>> so later conversions are fast, enabling quick iterations when fine-tuning >>>>> the conversion script. >>>>> >>>> >>>> Hence all developers are recommended to try to run the conversion >>>> script for their favorite (open and closed) tickets, and check if the >>>> conversion is done correctly. If you spot a conversion error, please >>>> report >>>> it to >>>> >>>> https://github.com/sagemath/trac-to-github/issues/18 >>>> >>>> -- 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/9195914a-3ee2-47cc-bbeb-9b5a7fec372en%40googlegroups.com.
