Skip to content

archive 2019.www.torproject.org permanently

The old website (https://2019.www.torproject.org/) has been replaced with the new, lektor-based website (https://www.torproject.org/) well over two years ago now. Since then (ie. since september 2019), only two commits were added to the git repository. And one of those was:

From 57b9f564bc03505e0189c2c22a9d2c7aa47c2ea1 Mon Sep 17 00:00:00 2001
From: gus <gus@torproject.org>
Date: Mon, 27 Apr 2020 15:48:17 -0400
Subject: Fix #26 - Notify users that 2019.www is an outdated website

I think it's time to completely archive the website. Concretely, that means it will not be migrated to GitLab CI, the Git repository will be disabled in gitolite (but still migrated to GitLab and archived), and no further changes should be performed on the site.

We can still make redirections if we need to redirect people away from old content, but I think whatever work that remained to be done on the site could have been done already, nothing is going to happen now that is going to make this magically worth it.

I bring this up now because otherwise this is one of the websites that would need to be migrated to GitLab CI. It's going to be much less work to simply archive it. If we want to revert that decision, we can still implement the site build in GitLab CI in the future, but I would strongly advise looking for other solutions instead.

Another reason I bring this up is that the site actually doesn't build at all right now, because of the tor.git repository change (tpo/tpa/team#40450 (closed)). It hardly seems worth fixing this in Jenkins just to turn around and have to redo the fix in GitLab CI again...

retirement checklist:

Edited by anarcat