Trac Wiki migration / archive
![](https://secure.gravatar.com/avatar/eba6eb871de2549c7447a8701352cd35.jpg?s=120&d=mm&r=g)
Hi, As part of the general effort to decommission our Trac website I have archived the wiki at the following repo https://github.com/twisted/trac-wiki-archive The plan is to mark the repo as "Archive" Any changes should be done in the twisted/twisted documentation or in the twisted.github.io website repo. The name of the repo can be renamed. Feel free to suggest better names or a better README file. ------- After we decommission the Trac instance we will implement a redirection for /trac/wiki/PAGE to a file on the archived GitHub repo. ------- There are already 2 PR https://github.com/twisted/twisted.github.io/pulls to migrate the wiki to Pelican or to Sphinx Feedback and a review is welcomed. Instead of a bulk conversion, my preference is for improving the "official"' Twisted documentation at https://docs.twistedmatrix.com/ with any valuable info from the wiki. Any non-documentation content should be converted into simple web pages for https://twisted.org/ ----------- Comments, questions ? Regards -- Adi Roiban
![](https://secure.gravatar.com/avatar/bcb6ef473ff1644fddee1b4e7c730b01.jpg?s=120&d=mm&r=g)
If we archive the repo in GitHub we won't be able to make changes to it, right? I think we may want to be able to change the existing pages e.g. have links up top to the new location of any information we migrate. Otherwise the plan sounds good to me. Thanks for taking this on! ---Tom On Thu, Jun 23, 2022, at 3:46 AM, Adi Roiban wrote:
![](https://secure.gravatar.com/avatar/eba6eb871de2549c7447a8701352cd35.jpg?s=120&d=mm&r=g)
Hi, On Sat, 25 Jun 2022 at 04:49, Tom Most <twm@freecog.net> wrote:
If we archive the repo in GitHub we won't be able to make changes to it, right? I think we may want to be able to change the existing pages e.g. have links up top to the new location of any information we migrate.
True. The repo will not be archived. I hope we will not forget to edit those pages with the link of the migrated content. Regards
-- Adi Roiban
![](https://secure.gravatar.com/avatar/bcb6ef473ff1644fddee1b4e7c730b01.jpg?s=120&d=mm&r=g)
If we archive the repo in GitHub we won't be able to make changes to it, right? I think we may want to be able to change the existing pages e.g. have links up top to the new location of any information we migrate. Otherwise the plan sounds good to me. Thanks for taking this on! ---Tom On Thu, Jun 23, 2022, at 3:46 AM, Adi Roiban wrote:
![](https://secure.gravatar.com/avatar/eba6eb871de2549c7447a8701352cd35.jpg?s=120&d=mm&r=g)
Hi, On Sat, 25 Jun 2022 at 04:49, Tom Most <twm@freecog.net> wrote:
If we archive the repo in GitHub we won't be able to make changes to it, right? I think we may want to be able to change the existing pages e.g. have links up top to the new location of any information we migrate.
True. The repo will not be archived. I hope we will not forget to edit those pages with the link of the migrated content. Regards
-- Adi Roiban
participants (2)
-
Adi Roiban
-
Tom Most