I appreciate that the migration from
github.com/sailfishos was handled better WRT announcements for specific actions and timelines provided in this thread, after the original announcement lacked a clear scope and any timelines.
After September, 14th we plan to shut down
git.sailfishos.org . This will make it a full 3 month period from the time when the repositories were migrated.
Why the haste for this shutdown?
git.sailfishos.org has been put into read-only mode (“archived”) three months ago: While this (in conjunction with the announcements in this thread) should have been sufficient time for copying content away, it does not and cannot resolve the need for references, especially to content, which was not migrated (i.e., everything, except for source code).
Side note: As Jolla uses the Free Software variant of Gitlab for their instance, there are no license fees, only the infrastructure cost of running a very lightly used server.
Example for this issue
Due to the migration away from
git.sailfishos.org, I had to re-issue two bug reports here at FSO (because the issue tracker at
github.com/sailfishos is switched off for most, although not all sub-projects, see e.g. the sailfish-browser): 1 and 2
But they both reference the original context at
git.sailfishos.org (comprised of issue reports there and related merge request comments there) to be fully comprehensible.
Suggestion how to handle this better
As Jolla’s understandable intention is to switch their Gitlab instance off sooner or later, postpone this step at least until the turn of the year (i.e., by 2,5 months or more).
This may provide sufficient time for open issues (e.g. the two mentioned above) to be read, understood and addressed by Jolla and / or others at their new location.
Additionally, the implementation of the redirects might be vastly improved:
To make it easier for people to find the new repositories, we will create redirects from the
git.sailfishos.org public repositories to the GitHub ones, and a redirect from
github.com/sailfishos . This should also keep the historical references alive.
This action / implementation will break all references (i.e., links), except those directed at the root of a specific project.
Plus it is tedious and error prone to create 702 redirects (the current number of sub-projects at GitHub), even when performed by a script. But these are the limitations of simple HTTP-redirects.
A proper implementation uses server-side scripting (e.g. Apaches’ or nginx’s
mod_rewrite or other means), see URL redirection - Wikipedia.
It would be great if Jolla implements such a server-side “link rewriter script” for all calls of “
https://github.com/sailfishos”-links: It simply has to transform a small part of a called link (in sed syntax:
Consequently this works for all links to source code (i.e., everything that was migrated), by performing e.g.,