public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] utilizing GH functionality that Gentoo infra does not provide
Date: Tue, 29 Mar 2022 12:29:23 -0700	[thread overview]
Message-ID: <CAAr7Pr-y7eQpWKBUhDOBT8wYreJ7cXwp1u-VBeHTGue_UHsnhw@mail.gmail.com> (raw)
In-Reply-To: <YkNIOS5E7gSH1cOk@vapier>

On Tue, Mar 29, 2022 at 10:56 AM Mike Frysinger <vapier@gentoo.org> wrote:
>
> starting a dedicated thread for
> https://archives.gentoo.org/gentoo-project/message/ec2b560480627371a7bda5c85924eddd
>
> GH provides a lot of functionality for free that Gentoo infra does not cover.
> these are particularly useful for projects that are used beyond Gentoo.

GH is non-free, and so in the spirit of the social contract, I do not
believe it should be used. Arguably it shouldn't be used now, but we
have not stood up an alternative. The alternative is currently in
alpha (see notes below.)

>
> * release management (e.g. distfiles hosting)

I agree this is a gap.

> * CI runs (e.g. GH actions)

We have CI but it's mostly not self-service and the primary issue on
the infra-side is always resources / people. I agree we should aim for
something more accessible.

> * Projects for task management

I'm not sure what this is (I haven't used it.) We use bugzilla for
task management (issues) and mailing lists (for discussion.) I'm not
sure github issues are "better" but they do have some advantages; I've
gotten complaints about bugzilla, particularly on mobile. Plus you
cannot reply to bugs easily via email.

For the time being the gitlab alpha does not intend to move issues out
of bugzilla; nor use gitlab for discussions; aside from discussions on
PRs (which will be on gitlab.)

> * possibly even Discussions since it'll provide a clear/scoped space for
> non-Gentoo users & devs. Gentoo forums are huge and require custom accts,
> and mailing lists are huge and a bit restrictive old timey.

We have an SSO solution (sso.gentoo.org) that we are rolling out for
developers, and our gitlab (in alpha testing) will support external
account providers (probably google, gitlab, github accounts.)

I'm honestly unsure how to receive feedback like "mailing lists are a
bit restrictive old timey". What does that mean?

 - It's hard to know which list to email.
 - I often have to subscribe to the list to post.
 - Hard to have pretty content in an email.

>
> this is all orthogonal to the git content itself (objects, branches, tags,
> etc...). those should remain in the read-only clobber mode that exists now.
>
> there is no downside for Gentoo here.  it's all functionality that can be
> had for free, does not introduce any risks, and many devs are already using
> GH heavily for Gentoo projects -- albeit, they don't do it under the Gentoo
> umbrella, they fork it into their own personal space and maintain it there.
> we shouldn't be forcing devs & projects away from Gentoo for such basic
> functionality.
> -mike

I think you present a 'free lunch' here and I'll just say "there is no
such thing as a free lunch." The downside is that we present Gentoo as
an open distro that doesn't depend on proprietary software, but is
developed using Github, a proprietary solution that provides all this
cool functionality that we don't have implemented in house. In general
that's not a sustainable approach. I get that we make tradeoffs
(firmware, drivers, being an obvious place where compromises are
made.) I'm not sure I'm willing to support this one.

I will tell you I have an alpha version of gitlab up, and I'm looking
for repos to mirror there. If you are satisfied with gitlab as the
platform to provide the features you want I'm happy to set up some
time to get your repos on gitlab; collect requirements, and figure out
what we need to deliver in our gitlab to host your repos (and
eventually all the Gentoo repos.)

Find me on signal or in #gentoo-gitlab on irc.libera.chat.

-A


  parent reply	other threads:[~2022-03-29 19:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 17:56 [gentoo-project] utilizing GH functionality that Gentoo infra does not provide Mike Frysinger
2022-03-29 18:26 ` Arthur Zamarin
2022-03-29 18:47   ` [gentoo-project] Gentoo's GitLab (was: utilizing GH functionality that Gentoo infra does not provide) Anna Vyalkova
2022-03-29 19:29 ` Alec Warner [this message]
2022-03-31  2:01   ` [gentoo-project] utilizing GH functionality that Gentoo infra does not provide Mike Frysinger
2022-03-29 19:36 ` Andreas K. Huettel
2022-03-31  2:01   ` Mike Frysinger
2022-03-31  8:21     ` David Seifert
2022-04-01  4:04       ` Mike Frysinger
2022-04-04 18:54         ` Andreas K. Huettel
2022-03-31 11:48 ` Maciej Barć
2022-03-31 16:43   ` Michael Jones
2022-03-31 18:07     ` Maciej Barć
2022-04-04 15:38       ` Andrew Ammerlaan
2022-04-01  1:27 ` Sam James
2022-04-01  1:28   ` Sam James
2022-04-01  4:29     ` Mike Frysinger
2022-04-01  4:17   ` Mike Frysinger
2022-04-01  5:52   ` Ulrich Mueller
2022-04-04 18:48   ` Andreas K. Huettel
2022-04-02 15:48 ` Matt Turner
2022-06-11 17:15 ` Luca Barbato

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=CAAr7Pr-y7eQpWKBUhDOBT8wYreJ7cXwp1u-VBeHTGue_UHsnhw@mail.gmail.com \
    --to=antarus@gentoo.org \
    --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