On Wed, 14 May 2025 16:50:18 +0100 J05HYYY <lovell.josh...@gmail.com> wrote: > Ideally we can still access the source code of replicant at the end of > all this in a state in which we can [try and] build it if we need too. > (I guess probably needs to be in git repos in a fashion suitable for > repo manifest, even if the git repos are ro too)
The Replicant source code isn't concerned by this migration as it was already on the VM at the FSF since a lot of years and both Replicant 4.2 and 6.0 have been known to build with that. To make sure we understand each other: the plan is to keep things online and improve the infrastructure, not shut it down. What is being converted to static is only the blog and potentially www.replicant.us as well but not redmine.replicant.us. And this is because (1) we want to self host and (2) for the blog, WordPress isn't adapted to our needs: we are 3 people in the Replicant steering committee and so in practice we try to review things before publishing them and WordPress doesn't make it easy to discuss the article by mail when it has not yet been published. It's also not easy to work offline on blog posts with WordPress, though thanks to code I wrote to facilitate the migration to new blog we can now do that and convert back to WordPress just before publishing. This is what we did for the last blog posts since quite some time already. > Thank you Denis. It would be nice (at least) to keep a ro/static copy > of everything online if possible. Or failing that, host dumps at > archive.org For the blog I plan to do something like that: not all the comments are under a free license so that is not easy to handle, so something like archive.org would work in any case, so it's good to have. Apart from that, most of the work is done and what's left is mostly deciding on how to best migrate and how to deal with the comments. The search function has been replaced by a tutorial that explains how to use git clone and git grep to find information in articles (that are now in markdown format) and the old links have been kept as well (you can try a blog post URL on blog.replicant.us and see if it works on blog.test.replicant.us, if it doesn't it's a bug and I need to fix it). One way to migrate would be to move the WordPress instance on wordpress.replicant.us and then move the new blog from blog.test.replicant.us to blog.replicant.us and then later on find a way to replace wordpress.replicant.us by something fully static without JavaScript or calls to an external avatar service, and then at some point ask OSUOSL to remove wordpress.replicant.us to reduce the amount of maintenance required. For the "FTP" where the releases are I'm not sure if archiving it to archive.org is really important as the same files would be served from the Replicant VM. And we can probably keep both location as long as possible, at least for the images older than the migration. > The wiki, redmine and forums give quite a bit of supporting > information, so would be good to have these, again ro or archived > somewhere at the very least. The wiki and forums won't go away. For the wiki there is a plan to migrate it to MediaWiki but it's far from complete so if in one year OSUOSL didn't manage to become sustainable we'll probably have to get a second VM at Libre En Communs (a french non-profit) just to run Redmine on PureOS crismon (because Redmine is packaged there). I found that PureOS crismon exited and also had redmine packaged only few days ago (few days after writing the initial mail). For the migration to MediaWiki the plan is to complete the code that can get the raw articles to git, and hope that we do capture well all the files, their history, dates, comment, etc, and then later on to convert these from the Redmine syntax to the MediaWiki syntax to reduce the amount of information loss (the old format would still be in the git history). Given the risks here finding a way to reliablity back it up in html form as well would also be a good idea. Denis.
pgppu3VCdm2NQ.pgp
Description: OpenPGP digital signature
_______________________________________________ Replicant mailing list Replicant@osuosl.org https://lists.osuosl.org/mailman/listinfo/replicant
