A good month ago, Olaf Meeuwissen wrote:
> Hi all,
So I thought I'd give you an update ;-)
> I have started work on some of the issues on the migration milestone I
> created on GitLab. Of course you can follow what's going on on the
> milestone directly (or the board) but I figured I'd post an update.
> : https://gitlab.com/sane-project/ops/milestones/1
# As for the board, I've been trying out the sane-project *group* board
# as opposed to the ops *project* board so you should now look at
# to get a picture of the current state.
> For starters, both the sane-backends and sane-frontends repositories
> on Alioth are now *read-only* and will no longer receive any updates.
> The developers should push to the corresponding repositories at
> GitLab.com from now on.
> Pushes to the Alioth repositories will now fail with an error message
> telling you how to switch your local checkout.
> # The website project will follow once we have a site set up on the
> # GitLab infra-structure. In the mean time, all these changes have
> # been reflected in the site's pages.
The website project has followed suit and the Alioth repository is now
read-only. This completes the transfer of *all* of the SANE project's
git repositories from Alioth to GitLab.com.
> All SANE project members on Alioth have received invitations to join the
> project on GitLab.com and a bit shy of half have already accepted. The
> rest will get another nudge soon. Please note that only project members
> can push to GitLab.com.
On this front, close to three quarters of the Alioth members have now
joined (or declined to join) the project on GitLab.com. The remaining
five have received several nudges by now and any outstanding invitations
will be closed after 2018-03-21 00:00 UTC.
# The initial invitation was issued on 2018-02-01, BTW.
> Release artifacts, [...]
Nothing changed in this department.
> In the mean time, I'm also looking at the possibility of migrating the
> Tracker items we have at Alioth. It doesn't look easy, but someone
> at GitLab.com (the Director of Strategic Partnerships) has contacted me
> with an offer to help. I'm not holding my breath but any help in this
> area is welcome.
> : https://gitlab.com/sane-project/ops/issues/10
I have been poking around in the FusionForge source code that powers
Alioth and found an interesting commit that may make migrating Alioth
issues a breeze. Well, almost at least. I'm waiting for the Alioth
maintainers to apply a patch so I can test. Details are in the issue
linked to above.
> If there is anything you think that's missing from the milestone or
> find fault with any of the attached release artifacts, feel free
> to submit a new issue. You don't have to be a SANE Project member.
> Simply login to GitLab.com and create a new issue.
> : https://gitlab.com/users/sign_in
> : https://gitlab.com/sane-project/ops/issues/new
This stands without change.
> Next up on my list is the website.
> : https://gitlab.com/sane-project/ops/issues/7
This issue has been closed after a good deal of mucking about with the
links in the webpages so they would work on Alioth and GitLab. While
working on this and testing stuff, I even got myself black-listed and
could not browse the site on Alioth for a while :-/
There is now a static SANE Project website that you can visit on
It should be identical to the one on Alioth. The Scanner Search
Engine will break as soon as Alioth goes off-line, though.
I have asked Allan to make the project's domain (sane-project.org)
point to the GitLab hosted website.
Hope this helps,
Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27
GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9
Support Free Software https://my.fsf.org/donate
Join the Free Software Foundation https://my.fsf.org/join
sane-devel mailing list: email@example.com
Unsubscribe: Send mail with subject "unsubscribe your_password"