2002
Tiki was first released in October 2002 using CVS on SourceForge
The path to the source code was: http://tikiwiki.cvs.sourceforge.net/tikiwiki/tiki/
2008
The Tiki project transitioned to Subversion (SVN) as of Tiki2, remaining at SourceForge. The platform was called Alexandria (internal name, not really promoted)
The path to the source code was https://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki/ (now inactive)
The Tiki Remote Instance Manager (TRIM) project was started, and it offered a tool to convert a CVS instance to SVN.
2013
Still at SourceForge, the source code moved to the Allura platformThe Allura project was here: https://sourceforge.net/projects/allura/
And later became Apache Allura
(from previous "Alexandria" platform). Ref.: Update from SVN pre 2013
The path to the source code became: https://sourceforge.net/p/tikiwiki/code/HEAD/tree/
2018
In May 2018, during the Tiki19 development cycle, a Git and SVN combined workflow using (SubGit) was implemented. The canonical source code is still SVN on SourceForge, but contributors progressively start collaborating via Git, on GitLab
The path to the source code became: https://gitlab.com/tikiwiki/tiki
After a while (not sure when), it was agreed no one should commit on SVN anymore, because 2-way sync would sometimes break.
In November 2018, Tiki Manager started as a revamp/fork/major upgrade of TRIM. Tiki Manager supports SVN and Git.
2019
Git becomes the default in Tiki Manager: https://gitlab.com/tikiwiki/tiki-manager/-/merge_requests/91
2023
Shortly after January 2023, the Git and SVN combined workflow will be retired, and there will no longer be any updates to SVN (except perhaps to add warnings to migrate). https://gitlab.com/tikiwiki/tiki is the canonical repo.
Other history: