public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Maciej Barć" <xgqt@gentoo.org>
To: gentoo-project@lists.gentoo.org, Mike Frysinger <vapier@gentoo.org>
Subject: Re: [gentoo-project] utilizing GH functionality that Gentoo infra does not provide
Date: Thu, 31 Mar 2022 13:48:25 +0200	[thread overview]
Message-ID: <a1ce4bf8-2bec-aba6-4543-dfb9cc6d8807@gentoo.org> (raw)
In-Reply-To: <YkNIOS5E7gSH1cOk@vapier>


[-- Attachment #1.1.1: Type: text/plain, Size: 2264 bytes --]


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

The way that I imagine it could happen would be quite weird/complicated 
to use. Mike, could you please expand on how you think this could work?


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


GURU already started experimenting with usage of GH's CI [1],
though I can't skip over a very irritating fact: GH seems to think that 
there is only one Linux-based OS ("runs-on: ubuntu-latest"). IMO it 
would be better to run the CI on Gentoo's containers - which is possible 
with GitLab's CI.
Also, on GitLab we do not have to pull images from official Docker 
registry [2].

But even just using GH's CI to list changes or do some minor check, 
(maybe do not ping everybody to oblivion) would be nice, because as Mike 
pointed out this is without any charge.

[1] https://github.com/gentoo/guru/tree/master/.github/workflows
[2] 
https://gitlab.com/src_prepare/racket/racket-overlay/-/blob/master/.gitlab-ci.yml#L18

On 3/29/22 7:56 PM, 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.
> 
> 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

-- 
Have a great day!

~ Maciej XGQT Barć

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 6297 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  parent reply	other threads:[~2022-03-31 11:48 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 ` [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ć [this message]
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=a1ce4bf8-2bec-aba6-4543-dfb9cc6d8807@gentoo.org \
    --to=xgqt@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