From: kuzetsa <kuzetsa@gmail.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Repo mirror & CI: official statement wrt GitHub
Date: Thu, 14 Jun 2018 15:55:19 -0400 [thread overview]
Message-ID: <8185f4b0-9d30-d15c-1f7b-331f2b9fafe3@gmail.com> (raw)
In-Reply-To: <1528529135.1261.34.camel@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 2421 bytes --]
On 06/09/2018 03:25 AM, Michał Górny wrote:
{...}
> As for moving mirrors elsewhere, I don't really see much of a purpose
> in doing that; at least as long as GitHub provides the service for free
> and doesn't complain about the space or the traffic involved.
> The primary use of the service is through git, so I don't really think
> it matters where the servers stand. Moving them elsewhere sounds like
> an unnecessary complexity for our users who'd have to update repos.conf.
{...}
> I'm ready and willing to support GitHub pull requests as long as there's
> interest in contributors using them, and the terms of service don't
> cause us any major trouble. That said, this particular project doesn't
> have much of a say how users decide to submit contributions and/or how
> developers wish to accept them.
{...}
> To those who believe moving out of GitHub is the only thing to do,
> I would like to remind you of two things. Firstly, if Microsoft indeed
> has malicious intent, then they've already won because you've let them
> fragment the community. Secondly, how do you know that GitLab won't be
> sold to another 'big player' soon enough?
This is sensible to me.
for non-developers who already contribute using a
git-based workflow, all github does (for example: for me
in-particular) is provide a convenient way to validate
that the commit was made by me and not someone else.
so long as repoman's default requirement that commits
should be signed, the github infrastructure knows which
PGP key is mine, and marks my commits as verified. for my
comfort, the increased effort to use a different workflow
(switching infra for git pushes) would be trivial, but
the burden is still a burden. a needless burden.
adding an //alternative// won't help me personally, but I
can only speak for myself. maybe some people feel more
strongly and would prefer a boycott. I'm not advocating
for this, but if some people opt to do so I'll probably
just keep using my current workflow. the added effort
to use a different method should be optional, I feel.
I see no utility to fix something which some people feel
isn't broken. so long as dropping github doesn't happen,
adding gitlab (or any other method) shouldn't affect me.
rather, it would add //an option// for people who feel the
need to use "not github", and that //can// be a positive.
--kuza
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-06-14 19:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-09 7:25 [gentoo-project] Repo mirror & CI: official statement wrt GitHub Michał Górny
2018-06-09 7:50 ` Ulrich Mueller
2018-06-09 7:52 ` Michał Górny
2018-06-09 9:11 ` Thomas Deutschmann
2018-06-11 12:15 ` Kristian Fiskerstrand
2018-06-11 13:28 ` Rich Freeman
2018-06-14 9:47 ` James Le Cuirot
2018-06-14 14:14 ` Alec Warner
2018-06-14 14:25 ` Mauricio Lima Pilla
2018-06-15 0:33 ` Thomas Deutschmann
2018-06-15 1:14 ` Aaron W. Swenson
2018-06-15 2:16 ` Alec Warner
2018-06-15 7:20 ` Kristian Fiskerstrand
2018-06-16 23:55 ` Virgil Dupras
2018-06-17 0:25 ` Rich Freeman
2018-06-16 21:58 ` Andreas K. Huettel
2018-06-16 23:14 ` Rich Freeman
2018-06-16 23:45 ` Alec Warner
2018-06-17 1:05 ` Brian Dolbec
2018-06-14 19:55 ` kuzetsa [this message]
2018-06-15 0:26 ` Thomas Deutschmann
2018-06-15 2:27 ` kuzetsa
2018-06-15 11:50 ` Thomas Deutschmann
2018-06-15 14:55 ` kuzetsa
2018-06-15 15:31 ` Rich Freeman
2018-06-15 16:03 ` kuzetsa
2018-06-15 16:11 ` Rich Freeman
2018-06-15 16:22 ` kuzetsa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8185f4b0-9d30-d15c-1f7b-331f2b9fafe3@gmail.com \
--to=kuzetsa@gmail.com \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox