Repository has been archived

Somewhat copied from a comment on another issue.

A bit of history of Transporter:

AFAIK (I wasn't around at the beginning) Compose developed this tool to allow customers to move data between deployment types as new database types were offered
There was quite a bit of development activity up until 2017. Then, I'm guessing, since Compose were being much more heavily integrated in to IBM goals changed and work stopped on the project.
In 2018 there was a bit of resurgence of activity as Compose also used this tool (under the hood) so customers could migrate from the Classic offering that was being shutdown
Many of the original contributors left IBM/Compose over the years
In advance of the shutdown of Compose there was a brief spell from the end of 2021 to mid 2022 where IBM/Compose dedicated some folk to work on this project again so we could help customers migrate from Compose to IBM Cloud. That's where the 1.0 release came from. The primary focus there was on Postgresql and MySQL.
Unfortunately internal focus then shifted again and no one was working on this as part of their job
There was a moment in 2023 when I thought that IBM would pick up Transporter again when looking at migration tooling for IBM Cloud Databases (the replacement offering for Compose), specifically with regards to MongoDB, but for whatever reason IBM decided to start anew with different tooling.
In 2023 Compose finally reached End of Life and was shut down completely. Since I was the last remaining technical person working on Compose I left this repo "open" for quite some time as I really hoped I'd be able to find personal time to work on it, but it's been months now and I just haven't had time at all.

So I've decided to archive this repository so it doesn't give the false impression it's being worked on. But by the magic of open-source it's available for anyone to fork and hopefully someone will as it's a neat idea.

compose / transporter

Repository has been archived #523