Re: [sane-devel] [janitorial] Relocating the SANE Project

[Louis Lagendijk]

On Fri, 2018-01-26 at 17:59 +0900, Olaf Meeuwissen wrote:
> Dear all,
> 
> TL;DR :: Let's move to GitLab.com!  Mailing list TBD.
> 
> # Apologies for the belated follow-up.  I planned to wait a week or
> so
> # to let the dust settle before following up but then Real Life got
> in
> # the way :-(
> 
> 
> I made a couple of suggestions and asked for feedback.  Apart from
> one
> off-list request to join the SANE project on GitLab.com, not one of
> the
> SANE developers has chimed in.  I will take that to mean that
> everyone
> will be fine with whatever gets chosen in the end.  Speak up if
> that's
> not the case!
> 
I am fine with whatever is chosen, as long as there is some description
of the expected work-flow, especilly for the handling of pull-requests.

> The non-developers that did follow up mentioned[1] Sourceforge as a
> possibility (and questioned[2] whether that was serious), offered
> help
> with moving the mailing list to Debian infra-structure[1] (thanks,
> btw!) and a preference for GitHub[3][4].
> 
sourceforge is attractive for its mailinglist capability. But as long
as we can find a working solution for that, I am fine. And we need to
move the web pages (especially supported devices) to an easily found
place.


BR, Louis

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] [janitorial] Relocating the SANE Project

[Olaf Meeuwissen]

Hi Markus,

Markus Heiser writes:

>> Am 26.01.2018 um 09:59 schrieb Olaf Meeuwissen :
>>
>> Dear all,
>>
>> TL;DR :: Let's move to GitLab.com!  Mailing list TBD.
>
> [ ... ]
>
>> The idea of putting a repository mirror on GitHub is interesting but I'm
>> not sure how pull requests and issues would work out if things are split
>> over multiple sites.
>
> Its not a show stopper: pull request can be handled by git itself,
> adding the github remote repo and pull the feature branch from there
> into the gitlab origin. Vice versa the github users are be able to
> fork from gitlab origin this way.
>
>  What I mean: there is no need for a github mirror.
>
> Stay with a Single-Point-of-Definition and do not mirror, it will
> only confuse the github users.

Thanks for your comments.  I realize that a github mirror is not
required.  It's just something I hadn't considered.  When I did, I
started to wonder how the web based merge/pull request workflows would
interoperate.  I have the impression that it will be confusing at the
very least, so, yes, let's start with a *single* location for the
project, at least until we're all settled on GitLab.com

Again, thanks for the feedback,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] [janitorial] Relocating the SANE Project

[Paul Newall]

I'm afraid I don't have any useful knowledge on this subject, so very 
happy that someone is thinking about it.


Paul Newall


On 26/01/18 16:56, Jörn-Ingo Weigert wrote:
It's ok with me, having a well known and used interface for pull/merge 
requests and on top support for mobile in either web and app form, I 
do really appreciate. So let's go to girls.com ! 
*Backpack shouldered*


Am 26.01.2018 9:59 vorm. schrieb "Olaf Meeuwissen" 
>:


Dear all,

TL;DR :: Let's move to GitLab.com!  Mailing list TBD.

# Apologies for the belated follow-up.  I planned to wait a week or so
# to let the dust settle before following up but then Real Life got in
# the way :-(

Now for the long story,

On 2018-01-08, Olaf Meeuwissen (that's me!) wrote:

> [ ... Alioth will be discontinued sometime in 2018-05 ... so]
> the SANE Project will no longer be able to:
>
>  - communicate via the mailing lists
>  - push commits to its official git repositories
>  - update the bug and feature requests trackers
>  - update its website
>
> So we have to move some place else for our project hosting but
where?

I made a couple of suggestions and asked for feedback. Apart from one
off-list request to join the SANE project on GitLab.com, not one
of the
SANE developers has chimed in.  I will take that to mean that everyone
will be fine with whatever gets chosen in the end.  Speak up if that's
not the case!

The non-developers that did follow up mentioned[1] Sourceforge as a
possibility (and questioned[2] whether that was serious), offered help
with moving the mailing list to Debian infra-structure[1] (thanks,
btw!) and a preference for GitHub[3][4].

There was also a fairly detailed account[5] of the pros and cons of
GitLab vs. GitHub as well as an offer to host mailing lists[6].
Finally, there was a hint on how to get release notifications from
GitHub using an RSS feed[7].

There was the notion that GitLab/GitHub issues and merge/pull requests
could meaningfully replace a large part of the mailing
lists[3][5], yet
having mailing lists (archives) around would be nice. Several people
also pointed out that moving[4][5] and/or mirroring[3] git
repositories
elsewhere would be easy and that GitHub Pages have their "quirks"[5].
Finally, the fact that GitLab.com supports logging in via GitHub,
Google, Twitter and BitBucket accounts was pointed out as a pro[5].
Neither GitHub nor the Debian GitLab instance provide this
(although the
latter could, in theory).

 [1]:

https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035897.html


 [2]:

https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035900.html


 [3]:

https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035911.html


 [4]:

https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035898.html


 [5]:

https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035899.html


 [6]:

https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035921.html


 [7]:

https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035912.html



Taking this all in, and putting the mailing lists issue aside for
a bit,
I still prefer moving to GitLab.com.  In terms of repository,
issues and
merge/pull request support it offers pretty much the same as
GitHub, but
on top of that allows you to log in using accounts users may have with
(selected) other services.  This, I think, lowers the barrier to
report
issues.  Furthermore, GitLab.com comes with CI out-of-the-box
(which is
used already by the current *unofficial* mirror, btw!).

The idea of putting a repository mirror on GitHub is interesting
but I'm
not sure how pull requests and issues would work out if things are
split
over multiple sites.

Back to mailing lists, I think that for the short term making use
of the
Alioth mail continuation project[8] is our best alternative,
although I
am not exactly clear on that project's status.  If I understand things
correctly the current list maintainer will be asked to opt in before

Re: [sane-devel] [janitorial] Relocating the SANE Project

[Jörn-Ingo Weigert]

It's ok with me, having a well known and used interface for pull/merge
requests and on top support for mobile in either web and app form, I do
really appreciate. So let's go to girls.com! *Backpack shouldered*

Am 26.01.2018 9:59 vorm. schrieb "Olaf Meeuwissen" <
paddy-h...@member.fsf.org>:

> Dear all,
>
> TL;DR :: Let's move to GitLab.com!  Mailing list TBD.
>
> # Apologies for the belated follow-up.  I planned to wait a week or so
> # to let the dust settle before following up but then Real Life got in
> # the way :-(
>
> Now for the long story,
>
> On 2018-01-08, Olaf Meeuwissen (that's me!) wrote:
>
> > [ ... Alioth will be discontinued sometime in 2018-05 ... so]
> > the SANE Project will no longer be able to:
> >
> >  - communicate via the mailing lists
> >  - push commits to its official git repositories
> >  - update the bug and feature requests trackers
> >  - update its website
> >
> > So we have to move some place else for our project hosting but where?
>
> I made a couple of suggestions and asked for feedback.  Apart from one
> off-list request to join the SANE project on GitLab.com, not one of the
> SANE developers has chimed in.  I will take that to mean that everyone
> will be fine with whatever gets chosen in the end.  Speak up if that's
> not the case!
>
> The non-developers that did follow up mentioned[1] Sourceforge as a
> possibility (and questioned[2] whether that was serious), offered help
> with moving the mailing list to Debian infra-structure[1] (thanks,
> btw!) and a preference for GitHub[3][4].
>
> There was also a fairly detailed account[5] of the pros and cons of
> GitLab vs. GitHub as well as an offer to host mailing lists[6].
> Finally, there was a hint on how to get release notifications from
> GitHub using an RSS feed[7].
>
> There was the notion that GitLab/GitHub issues and merge/pull requests
> could meaningfully replace a large part of the mailing lists[3][5], yet
> having mailing lists (archives) around would be nice.  Several people
> also pointed out that moving[4][5] and/or mirroring[3] git repositories
> elsewhere would be easy and that GitHub Pages have their "quirks"[5].
> Finally, the fact that GitLab.com supports logging in via GitHub,
> Google, Twitter and BitBucket accounts was pointed out as a pro[5].
> Neither GitHub nor the Debian GitLab instance provide this (although the
> latter could, in theory).
>
>  [1]: https://lists.alioth.debian.org/pipermail/sane-devel/2018-
> January/035897.html
>  [2]: https://lists.alioth.debian.org/pipermail/sane-devel/2018-
> January/035900.html
>  [3]: https://lists.alioth.debian.org/pipermail/sane-devel/2018-
> January/035911.html
>  [4]: https://lists.alioth.debian.org/pipermail/sane-devel/2018-
> January/035898.html
>  [5]: https://lists.alioth.debian.org/pipermail/sane-devel/2018-
> January/035899.html
>  [6]: https://lists.alioth.debian.org/pipermail/sane-devel/2018-
> January/035921.html
>  [7]: https://lists.alioth.debian.org/pipermail/sane-devel/2018-
> January/035912.html
>
> Taking this all in, and putting the mailing lists issue aside for a bit,
> I still prefer moving to GitLab.com.  In terms of repository, issues and
> merge/pull request support it offers pretty much the same as GitHub, but
> on top of that allows you to log in using accounts users may have with
> (selected) other services.  This, I think, lowers the barrier to report
> issues.  Furthermore, GitLab.com comes with CI out-of-the-box (which is
> used already by the current *unofficial* mirror, btw!).
>
> The idea of putting a repository mirror on GitHub is interesting but I'm
> not sure how pull requests and issues would work out if things are split
> over multiple sites.
>
> Back to mailing lists, I think that for the short term making use of the
> Alioth mail continuation project[8] is our best alternative, although I
> am not exactly clear on that project's status.  If I understand things
> correctly the current list maintainer will be asked to opt in before
> Alioth is discontinued.
>
> I have also considered moving to lists.debian.org but in that case we
> probably won't be able to make the list subscriber-only or moderate
> incoming posts[9][10].
>
>  [8]: https://wiki.debian.org/Alioth/MailingListContinuation
>  [9]: https://wiki.debian.org/Alioth#Mailing_lists
>  [10]: https://www.debian.org/MailingLists/HOWTO_start_list
>
> In either case, sane-commit is extremely likely to disappear (you can
> use the commit notification functionality of GitLab instead).  As for
> sane-standard (which has seen less than 100KB gzipped traffic since July
> 2004!), I think it doesn't serve any purpose.  SANE standard discussions
> can be held on sane-devel.  The sane-announce list sees even less
> traffic but does serve a well-defined purpose (prevent announcements
> from "drowning" in the other traffic) and should be migrated together
> with sane-devel.
>
> Anyway, I'll check the status on [8] and look at some other mailing list
> hosting solutions but 

Re: [sane-devel] [janitorial] Relocating the SANE Project

[Markus Heiser]

> Am 26.01.2018 um 09:59 schrieb Olaf Meeuwissen :
> 
> Dear all,
> 
> TL;DR :: Let's move to GitLab.com!  Mailing list TBD.

[ ... ]

> Taking this all in, and putting the mailing lists issue aside for a bit,
> I still prefer moving to GitLab.com.  In terms of repository, issues and
> merge/pull request support it offers pretty much the same as GitHub, but
> on top of that allows you to log in using accounts users may have with
> (selected) other services.  This, I think, lowers the barrier to report
> issues.  Furthermore, GitLab.com comes with CI out-of-the-box (which is
> used already by the current *unofficial* mirror, btw!).
> 
> The idea of putting a repository mirror on GitHub is interesting but I'm
> not sure how pull requests and issues would work out if things are split
> over multiple sites.

Its not a show stopper: pull request can be handled by git itself,
adding the github remote repo and pull the feature branch from there
into the gitlab origin. Vice versa the github users are be able to
fork from gitlab origin this way. 

 What I mean: there is no need for a github mirror. 

Stay with a Single-Point-of-Definition and do not mirror, it will
only confuse the github users.

-- Markus --



-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] [janitorial] Relocating the SANE Project

[Olaf Meeuwissen]

Dear all,

TL;DR :: Let's move to GitLab.com!  Mailing list TBD.

# Apologies for the belated follow-up.  I planned to wait a week or so
# to let the dust settle before following up but then Real Life got in
# the way :-(

Now for the long story,

On 2018-01-08, Olaf Meeuwissen (that's me!) wrote:

> [ ... Alioth will be discontinued sometime in 2018-05 ... so]
> the SANE Project will no longer be able to:
>
>  - communicate via the mailing lists
>  - push commits to its official git repositories
>  - update the bug and feature requests trackers
>  - update its website
>
> So we have to move some place else for our project hosting but where?

I made a couple of suggestions and asked for feedback.  Apart from one
off-list request to join the SANE project on GitLab.com, not one of the
SANE developers has chimed in.  I will take that to mean that everyone
will be fine with whatever gets chosen in the end.  Speak up if that's
not the case!

The non-developers that did follow up mentioned[1] Sourceforge as a
possibility (and questioned[2] whether that was serious), offered help
with moving the mailing list to Debian infra-structure[1] (thanks,
btw!) and a preference for GitHub[3][4].

There was also a fairly detailed account[5] of the pros and cons of
GitLab vs. GitHub as well as an offer to host mailing lists[6].
Finally, there was a hint on how to get release notifications from
GitHub using an RSS feed[7].

There was the notion that GitLab/GitHub issues and merge/pull requests
could meaningfully replace a large part of the mailing lists[3][5], yet
having mailing lists (archives) around would be nice.  Several people
also pointed out that moving[4][5] and/or mirroring[3] git repositories
elsewhere would be easy and that GitHub Pages have their "quirks"[5].
Finally, the fact that GitLab.com supports logging in via GitHub,
Google, Twitter and BitBucket accounts was pointed out as a pro[5].
Neither GitHub nor the Debian GitLab instance provide this (although the
latter could, in theory).

 [1]: 
https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035897.html
 [2]: 
https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035900.html
 [3]: 
https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035911.html
 [4]: 
https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035898.html
 [5]: 
https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035899.html
 [6]: 
https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035921.html
 [7]: 
https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035912.html

Taking this all in, and putting the mailing lists issue aside for a bit,
I still prefer moving to GitLab.com.  In terms of repository, issues and
merge/pull request support it offers pretty much the same as GitHub, but
on top of that allows you to log in using accounts users may have with
(selected) other services.  This, I think, lowers the barrier to report
issues.  Furthermore, GitLab.com comes with CI out-of-the-box (which is
used already by the current *unofficial* mirror, btw!).

The idea of putting a repository mirror on GitHub is interesting but I'm
not sure how pull requests and issues would work out if things are split
over multiple sites.

Back to mailing lists, I think that for the short term making use of the
Alioth mail continuation project[8] is our best alternative, although I
am not exactly clear on that project's status.  If I understand things
correctly the current list maintainer will be asked to opt in before
Alioth is discontinued.

I have also considered moving to lists.debian.org but in that case we
probably won't be able to make the list subscriber-only or moderate
incoming posts[9][10].

 [8]: https://wiki.debian.org/Alioth/MailingListContinuation
 [9]: https://wiki.debian.org/Alioth#Mailing_lists
 [10]: https://www.debian.org/MailingLists/HOWTO_start_list

In either case, sane-commit is extremely likely to disappear (you can
use the commit notification functionality of GitLab instead).  As for
sane-standard (which has seen less than 100KB gzipped traffic since July
2004!), I think it doesn't serve any purpose.  SANE standard discussions
can be held on sane-devel.  The sane-announce list sees even less
traffic but does serve a well-defined purpose (prevent announcements
from "drowning" in the other traffic) and should be migrated together
with sane-devel.

Anyway, I'll check the status on [8] and look at some other mailing list
hosting solutions but in the mean-time, how does everyone feel about
moving to GitLab.com?

Hope this helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org

Re: [sane-devel] [janitorial] Relocating the SANE Project

[Julian H. Stacey]

Olaf Meeuwissen wrote:
> Since 2003-09-06, the SANE Project has been kindly hosted on Debian's
> Alioth.  The Debian project has deprecated[1] this service and intends
> to discontinue[*] it when Debian Wheezy becomes EOL.  While that seems

> That is, if we don't act, the SANE Project will no longer be able to:
>  - communicate via the mailing lists
>  - push commits to its official git repositories
>  - update the bug and feature requests trackers
>  - update its website
> 
> So we have to move some place else for our project hosting but where?

In case you get stuck, but hoping you'll get better offers elsewhere:

I could run a couple of extra sane mail lists here:
http://mailman.berklix.org/mailman/listinfo
You might find other offers from those on
https://mail.python.org/mailman/listinfo/mailman-users

I run apache with various virtual domains http://www.berklix.eu/Default/
but not giving out root, & no time to maintain interactive script support.

I dont run git.

rsync receives FreeBSD CTM deltas http://www.berklix.org/ctm/

Cheers,
Julian
-- 
Julian H. Stacey, Computer Consultant, BSD Linux Unix Systems Engineer, Munich
 http://berklix.eu/brexit/ UK stole 3,700,000 votes; 700,000 from Brits in EU.
 http://berklix.eu/queen/  Please sign petition to Queen: Help get votes back.

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] [janitorial] Relocating the SANE Project

[Arseniy Skvortsov]

However, a sane-releases@ is still interesting for package
maintainers. I dunno a github feature for watching new releases.


One can use RSS feeds for that, like
https://github.com/kkaempf/sane-backends/releases.atom

--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] [janitorial] Relocating the SANE Project

[Luiz Angelo Daros de Luca]

I also prefer GitHub. Anyway, someone will create a SANE mirror project
there and other will fork from it instead of main git repo. It's not a
marriage, just conviene.

I would like to keep ML but issue and PR can replace most of ML use for dev
and users help. However, a sane-releases@ is still interesting for package
maintainers. I dunno a github feature for watching new releases.

Regards,

Em ter, 9 de jan de 2018 14:15, Markus Heiser 
escreveu:

>
> > Am 08.01.2018 um 22:40 schrieb Jeff :
> >
> > On 08/01/18 08:46, Olaf Meeuwissen wrote:
> >> What are your preferences?  Feel free to mention other options.
> >
> > There is also Sourceforge.
>
> IMO sourceforge is a step backward, not really your preference, or?
>
> -- Markus --
>
> --
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>  to sane-devel-requ...@lists.alioth.debian.org
>
-- 

Luiz Angelo Daros de Luca
luizl...@gmail.com
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] [janitorial] Relocating the SANE Project

[Markus Heiser]

> Am 08.01.2018 um 22:40 schrieb Jeff :
> 
> On 08/01/18 08:46, Olaf Meeuwissen wrote:
>> What are your preferences?  Feel free to mention other options.
> 
> There is also Sourceforge.

IMO sourceforge is a step backward, not really your preference, or?

-- Markus --

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] [janitorial] Relocating the SANE Project

[Markus Heiser]

Hi,

nothing 'new' just my 2cent ...

> Am 08.01.2018 um 08:46 schrieb Olaf Meeuwissen :
> 
> Dear all,
> 
> # Project members explicitly BCC:d, just in case they don't subscribe.
> # Project admins CC:d to make sure they take note ;-)
> # Replies to the list, please.
> 
> Since 2003-09-06, the SANE Project has been kindly hosted on Debian's
> Alioth.  The Debian project has deprecated[1] this service and intends
> to discontinue[*] it when Debian Wheezy becomes EOL.  While that seems
> to be slated[2] for 2018-05-31, the Alioth wiki page's News[3] section
> states 2018-05-01 for Alioth itself and 2018-02-01 for mailing lists.
> 
> [*]: It is not quite clear what that exactly entails but at best the
>  service will become read-only.
> 
> A Debian-backed GitLab-based replacement has been announced[4] in beta
> and it looks like there may be a temporary continuation of the mailing
> lists[5] but *nothing* will be migrated automatically.  Everything has
> to be done explicitly.
> 
> That is, if we don't act, the SANE Project will no longer be able to:
> 
> - communicate via the mailing lists
> - push commits to its official git repositories
> - update the bug and feature requests trackers
> - update its website
> 
> So we have to move some place else for our project hosting but where?
> 
> The Debian-backed GitLab-based replacement[6] is one option.  Two others
> are GitLab.com[7] and GitHub.com[8].  None of these provides support for
> mailing lists so we need something else for that.

about mailing-lists ...

SANE maintainer & code-contriubutor POV: 
- con: ML must be maintained
- con: Pull Request are 'local & handmade' no (public) CI for PR & discussion

rare visitors POV:
- pro: No git-hoster (github.com or gitlab.com) account needed / just a mail to 
ML

IMO overall: maintain issue tracker, PRs and ... from a git-hoster in
parallel with a ML is a lot of work and mostly confusing. Thats why
I would recommend to drop the ML when moving to a git-hoster. The drawback;
all contributors (even rare visitors) will need a account by the git-hoster.
Another drawback: the old history of the ML will be lost.

So IMO this must be the first decision; drop ML or search for an alternative.


>  Migrating to Debian's
> temporary continuation is one option.  Any other suggestions?  As for
> the website, all three (will) have support for *static* webpages.  The
> trackers are covered by the issue systems of all three.
> 
> [1]: https://wiki.debian.org/Alioth#Deprecation_of_Alioth
> [2]: https://wiki.debian.org/LTS
> [3]: https://wiki.debian.org/Alioth#News
> [4]: https://lists.debian.org/debian-devel-announce/2017/12/msg3.html
> [5]: https://wiki.debian.org/Alioth/MailingListContinuation
> [6]: https://salsa.debian.org
> [7]: https://gitlab.com
> [8]: https://github.com
> 
> You may remember that I set up an *unofficial* SANE Project group[9] on
> GitLab.com to play around with GitLab CI that mirrors the project's git
> repositories on Alioth.  We could use that.  I have also created a stub
> on GitHub.com[10] and two on Debian's GitLab[11][12] (which enforces a
> *-team naming convention for groups :-() to reserve the names.
> 
> [9]: https://gitlab.com/sane-project
> [10]: https://github.com/sane-project
> [11]: https://salsa.debian.org/sane-team
> [12]: https://salsa.debian.org/sane-project-team
> 
> I am personally in favour of using something we could in principle run
> ourselves. That would rule out GitHub.com.


What I do: I host my public repos at github. Locally I have a self hosted
gitlab instance. It is very easy to move from github to gitlab including
issue tracker and other meta data.

  https://docs.gitlab.com/ee/user/project/import/github.html

What I mean: if you decide for github.com and there comes a day you are
pissed of by, it is easy to move from github.com to gitlab.com
or to a self hosted gitlab instance.


>   Also, it is not clear yet
> when website hosting becomes possible or to what extent Debian's GitLab
> instance will provide CI runners (needed to publish the website), so
> *my* preference is GitLab.com (steering clear of its enterprise-only
> functionality).
> 
> What are your preferences?  Feel free to mention other options.

As said I'am using self-hosted gitlab and github.com. For public
things I prefer github.com over gitlab.com. My impression is, that
there are more potential contributors on github.com because its
more popular.

Yes, I know there are static pages with github.io but I don't
like them. To often I see non-reproducible errors where URLs
are not working (very strange behavior I have seen there ..
is it only to me? .. I don't know).

Another "pro" for gitlab.com I see is omniauth, so rare contributors
can use their github.com account to login gitlab.com: 

  https://docs.gitlab.com/ce/integration/omniauth.html

At the end I have to say, that I like to prefer the gitlab way.
Anyway, the truth is that github.com is more popular. As a
result 

Re: [sane-devel] [janitorial] Relocating the SANE Project

[Johannes Meixner]

Hello,

On Jan 8 16:46 Olaf Meeuwissen wrote (excerpt):

So we have to move some place else for our project hosting but where?

...

[10]: https://github.com/sane-project

...

What are your preferences?


my personal selfish preference is GitHub
because so much other stuff is already there
( "billions of flies can't be wrong" ;-)
which makes it easier to work on various
different things:

 "One Place to rule them all, One Place to find them,
  One Place to bring them all and in the darkness bind them.
  In the land of GitHub where the Sources lie."

Of course I know "easier" does not mean it is "better"
in particular not from a strict free software point of view:
https://www.gnu.org/software/repo-criteria-evaluation.html

But I think because in the end it is plain 'git'
nothing really evil could happen if at some day
GitHub might become unusable for free software
(in this case things could be hosted anywhere else)
and because it is free software I don't care if GitHub
monitors and evaluates all what goes on in GitHub
because all is public anyway (I see no real differece
compared to a public mailing list with public archives).


Kind Regards
Johannes Meixner
--
SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard,
Graham Norton - HRB 21284 (AG Nuernberg)


--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] [janitorial] Relocating the SANE Project

[Jeff]

On 08/01/18 08:46, Olaf Meeuwissen wrote:
> What are your preferences?  Feel free to mention other options.

There is also Sourceforge.

I don't have much, if any, free time, but I am a DD, so if help was
needed with the mailing list replacement using Debian infrastructure, I
might be able to lend a hand.

Regards

Jeff



signature.asc
Description: OpenPGP digital signature
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org