[sane-devel] [janitorial] Alioth → GitLab Migration Update

Ralph Little littlesincanada at yahoo.co.uk
Fri Feb 9 17:01:11 UTC 2018

Hi,Thanks for the update Olaf. 
I'm a lurker rather than a developer so I appreciate the information.


      From: Olaf Meeuwissen <paddy-hack at member.fsf.org>
 To: Sane Development <sane-devel at lists.alioth.debian.org> 
 Sent: Friday, February 9, 2018 4:00 AM
 Subject: [sane-devel] [janitorial] Alioth → GitLab Migration Update
Hi all,

I have started work on some of the issues on the migration milestone I
created on GitLab[1].  Of course you can follow what's going on on the
milestone directly (or the board[2]) but I figured I'd post an update.

  [1]: https://gitlab.com/sane-project/ops/milestones/1
  [2]: https://gitlab.com/sane-project/ops/boards?milestone_title=Alioth%20%E2%86%92%20GitLab%20Migration

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.

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.

Release artifacts, i.e. source tarballs, have been attached to their
corresponding release tags for both backends[3] and frontends[4].
Various checksums have been added as well as some release notes.

  [3]: https://gitlab.com/sane-project/backends/tags?search=RELEASE
  [4]: https://gitlab.com/sane-project/frontends/tags?search=RELEASE

In the mean time, I'm also looking at the possibility of migrating the
Tracker items we have at Alioth[5].  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.

  [5]: https://gitlab.com/sane-project/ops/issues/10

If there is anything you think that's missing from the milestone[1] or
find fault with any of the attached release artifacts[3][4], feel free
to submit a new issue[6].  You don't have to be a SANE Project member.
Simply login to GitLab.com[7] and create a new issue[6].

  [6]: https://gitlab.com/users/sign_in
  [7]: https://gitlab.com/sane-project/ops/issues/new

Next up on my list is the website[8].

  [8]: https://gitlab.com/sane-project/ops/issues/7

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: sane-devel at lists.alioth.debian.org
Unsubscribe: Send mail with subject "unsubscribe your_password"
            to sane-devel-request at lists.alioth.debian.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20180209/6b11201c/attachment.html>

More information about the sane-devel mailing list