From: Arthur Zamarin <arthurzam@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: vapier@gentoo.org
Subject: Re: [gentoo-project] utilizing GH functionality that Gentoo infra does not provide
Date: Tue, 29 Mar 2022 21:26:11 +0300 [thread overview]
Message-ID: <a372c696-48f4-ae61-b49c-80168c05dcde@gentoo.org> (raw)
In-Reply-To: <YkNIOS5E7gSH1cOk@vapier>
[-- Attachment #1.1: Type: text/plain, Size: 2535 bytes --]
On 29/03/2022 20.56, Mike Frysinger 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.
>
> * release management (e.g. distfiles hosting)
> * CI runs (e.g. GH actions)
> * Projects for task management
> * 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.
I myself agree on this list. I find some of those features quite nice
and helping for my developments for Gentoo, so I can understand why we
would like them.
> 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.
I know there exist some social contract by Gentoo, which might have
issues with us using GitHub, but I'm not sure I can fully explain it, so
I will leave it for others to explain or debate.
I know this is a future project (with something running currently [1]),
but one day we will have a running Gentoo's GitLab system. I think most
of the features listed above are currently working in the current
instance, with various extra nice things (like bugzilla and IRC
integration), and I think the main thing that isn't setup ready is CI.
GitLab also has mirroring support (I still didn't manage to setup it,
but my experience with such things is very low), so people could use
GitLab mainly, with mirror on GitHub, which might improve our "image".
To summarize my long text, I think that even if we open the GitHub
features (I don't have opinion on it), I think in some time, most of us
will move into Gentoo's GitLab.
> -mike
Thanks for opening this discussion - nice reading from you :)
[1] https://gitlab.gentoo.org/
--
Arthur Zamarin
arthurzam@gentoo.org
Gentoo Linux developer (Python, GURU, Arch Teams)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-03-29 18:26 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 [this message]
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 ` [gentoo-project] utilizing GH functionality that Gentoo infra does not provide Alec Warner
2022-03-31 2:01 ` 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=a372c696-48f4-ae61-b49c-80168c05dcde@gentoo.org \
--to=arthurzam@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=vapier@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