Hi,
This is just a quick heads up to remind everyone that our dear old Trac instance, https://trac.torproject.org/ is retiring in two days, on December 9th, as announced 6 months ago[1].
[1]: https://lists.torproject.org/pipermail/tor-project/2020-June/002866.html
Around that time, Trac was put in "read-only mode", in that no changes were allowed through the web interface whatsoever. We have heard approximately zero complaints about the change: while some people have concerns about GitLab and lots of things could be improved there, it seems no one is actually missing poor old Trac.
As much of the Trac content as possible was migrated into GitLab. An integral copy of the [Trac wiki] and [Trac issues] will be kept as is in GitLab. Most of those issues were migrated to their own projects, and lots of the wiki content was spread out to different, team-specific wikis (which makes the content a bit hard to find, see [issue 66] for details on that).
[Trac wiki]: https://gitlab.torproject.org/legacy/trac/-/wikis/home [Trac issues]: https://gitlab.torproject.org/legacy/trac/-/issues [issue 66]: https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/66
Trac was also thoroughly archived on the Wayback machine[2] for those cases where you really only know how to find something by looking at it "the Trac way". This should also salvage some pages that do not get rendered quite right in the GitLab migration, which happens.
[2]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40003
The plan, right now, is to redirect the Wiki and issue URLs into GitLab's relevant legacy project, and everything else to the GitLab front page. (It is considered bad practice to hotwire old sites into the wayback machine: we prefer to refer to live data instead, even though that old data is still available.)
The actual virtual machine where Trac is hosted will be destroyed 30 days after the redirections are in place, as an exceptional measure considering the service Trac has given us over the years. Absolutely do tell us if you feel there is some critical data that would be lost when that happens, something that was not correctly migrated to Gitlab *and* would not be available through the Wayback machine.
Further progress updates on the life and tribulation of troodi, the machine that hosted trac.torproject.org all those years, will only be posted in this ticket:
https://gitlab.torproject.org/tpo/tpa/team/-/issues/34373
## Post-scriptum: history
People might also be interested in the history of bug trackers at the Tor project:
* lost in the mists of time: migration from Bugzilla to Flyspray (40 tickets) * 2010-04-23: [migration from Flyspray to Trac completed][] (last Flyspray ticket is [1393][], first Trac ticket is [2000][]) * 2016-11-29: [first request to setup a GitLab server][] * ~2017: oniongit.eu (warning: squatted domain) deployed to test GitLab with the network team, considered as gitlab.torproject.net but ultimately [abandoned][] * 2019-02-28: `gitlab-01` AKA dip.torproject.org test server setup ([issue 29400][]), following the [Brussels meeting][] * 2019-07-17: GitLab discussed again at the [Stockholm meeting][] * 2019-07-29: Formal proposal to deploy GitLab [sent to tor-project][], no objection * 2020-03-05: GitLab migrated from `gitlab-01` (AKA "dip") to `gitlab-02` using the Omnibus package * 2020-04-27: `gitlab-01` retired * 2020-06-13 19:00UTC: [Trac readonly][] * 2020-06-13 02:25UTC: Trac tickets migrated (32401 tickets, last ticket id is [34451][], first GitLab legacy project ticket id is 40000) * 2020-06-14 21:22UTC: Trac wiki migrated * 2020-06-15 18:30UTC: bugs.torproject.org redirects to gitlab * 2020-06-16 02:15UTC: GitLab launch announced to tor-internal * 2020-06-17 12:33UTC: Archivebot starts crawling all tickets of, and the entire Trac website * 2020-06-23: Archivebot completes the full Trac crawl, Trac is fully archived on the Internet Archive
Coming up next:
* 2020-09-09: Trac redirects to GitLab * 2021-01-09: Trac server, troodi, destroyed
[migration from Flyspray to Trac completed]: https://lists.torproject.org/pipermail/tor-dev/2010-April/000183.html [1393]: https://bugs.torproject.org/1393 [2000]: https://bugs.torproject.org/2000 [first request to setup a GitLab server]: https://gitlab.torproject.org/tpo/tpa/services/-/issues/20821 [abandoned]: https://gitlab.torproject.org/tpo/tpa/services/-/issues/21840 [issue 29400]: https://gitlab.torproject.org/tpo/tpa/services/-/issues/29400 [Brussels meeting]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsAdmin... [Stockholm meeting]: https://gitlab.torproject.org/legacy/trac/-/wikis/org/meetings/2019Stockholm... [sent to tor-project]: https://lists.torproject.org/pipermail/tor-project/2019-July/002407.html [Trac readonly]: https://lists.torproject.org/pipermail/tor-project/2020-June/002872.html [34451]: https://bugs.torproject.org/34451
A.
Hi,
TL;DR: Trac has been shutdown and will be destroyed soon.
This has now been done: trac.torproject.org redirects to GitLab, and the original virtual host hosting Trac has been shutdown. The disks will be destroyed in 30 days (on Thu Jan 28 20:54:00 2021 UTC), and the backups will be destroyed in 180 days (on Sun Jun 27 21:23:00 2021 UTC).
It has just become harder to restore anything from Trac. But it will become much, much harder as time goes. So, really, if there is anything missing, do let us know before the *first* deadline, because restoring from backups might involve reverse-engineering the Trac storage mechanisms (database? file attachments?) or maybe even reinstalling the entire VM.
Or you would be too late and the data will just be gone. Nostalgics and nervous archivists are welcome to browse the internet archive copy:
https://web.archive.org/web/2/https://trac.torproject.org/
If there's anything there that you can't find in GitLab:
https://gitlab.torproject.org/
or in the Legacy project:
https://gitlab.torproject.org/legacy/trac/
... issues:
https://gitlab.torproject.org/legacy/trac/-/issues
or wiki:
https://gitlab.torproject.org/legacy/trac/-/wikis/home
... NOW is the time to speak, or be silent forever.
A.
On 2020-12-07 14:46:26, Antoine Beaupré wrote:
Hi,
This is just a quick heads up to remind everyone that our dear old Trac instance, https://trac.torproject.org/ is retiring in two days, on December 9th, as announced 6 months ago[1].
Around that time, Trac was put in "read-only mode", in that no changes were allowed through the web interface whatsoever. We have heard approximately zero complaints about the change: while some people have concerns about GitLab and lots of things could be improved there, it seems no one is actually missing poor old Trac.
As much of the Trac content as possible was migrated into GitLab. An integral copy of the [Trac wiki] and [Trac issues] will be kept as is in GitLab. Most of those issues were migrated to their own projects, and lots of the wiki content was spread out to different, team-specific wikis (which makes the content a bit hard to find, see [issue 66] for details on that).
Trac was also thoroughly archived on the Wayback machine[2] for those cases where you really only know how to find something by looking at it "the Trac way". This should also salvage some pages that do not get rendered quite right in the GitLab migration, which happens.
The plan, right now, is to redirect the Wiki and issue URLs into GitLab's relevant legacy project, and everything else to the GitLab front page. (It is considered bad practice to hotwire old sites into the wayback machine: we prefer to refer to live data instead, even though that old data is still available.)
The actual virtual machine where Trac is hosted will be destroyed 30 days after the redirections are in place, as an exceptional measure considering the service Trac has given us over the years. Absolutely do tell us if you feel there is some critical data that would be lost when that happens, something that was not correctly migrated to Gitlab *and* would not be available through the Wayback machine.
Further progress updates on the life and tribulation of troodi, the machine that hosted trac.torproject.org all those years, will only be posted in this ticket:
https://gitlab.torproject.org/tpo/tpa/team/-/issues/34373
## Post-scriptum: history
People might also be interested in the history of bug trackers at the Tor project:
- lost in the mists of time: migration from Bugzilla to Flyspray (40 tickets)
- 2010-04-23: [migration from Flyspray to Trac completed][] (last Flyspray ticket is [1393][], first Trac ticket is [2000][])
- 2016-11-29: [first request to setup a GitLab server][]
- ~2017: oniongit.eu (warning: squatted domain) deployed to test GitLab with the network team, considered as gitlab.torproject.net but ultimately [abandoned][]
- 2019-02-28: `gitlab-01` AKA dip.torproject.org test server setup ([issue 29400][]), following the [Brussels meeting][]
- 2019-07-17: GitLab discussed again at the [Stockholm meeting][]
- 2019-07-29: Formal proposal to deploy GitLab [sent to tor-project][], no objection
- 2020-03-05: GitLab migrated from `gitlab-01` (AKA "dip") to `gitlab-02` using the Omnibus package
- 2020-04-27: `gitlab-01` retired
- 2020-06-13 19:00UTC: [Trac readonly][]
- 2020-06-13 02:25UTC: Trac tickets migrated (32401 tickets, last ticket id is [34451][], first GitLab legacy project ticket id is 40000)
- 2020-06-14 21:22UTC: Trac wiki migrated
- 2020-06-15 18:30UTC: bugs.torproject.org redirects to gitlab
- 2020-06-16 02:15UTC: GitLab launch announced to tor-internal
- 2020-06-17 12:33UTC: Archivebot starts crawling all tickets of, and the entire Trac website
- 2020-06-23: Archivebot completes the full Trac crawl, Trac is fully archived on the Internet Archive
Coming up next:
- 2020-09-09: Trac redirects to GitLab
- 2021-01-09: Trac server, troodi, destroyed
A.
-- Antoine Beaupré torproject.org system administration
tor-project@lists.torproject.org