From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] utilizing GH functionality that Gentoo infra does not provide
Date: Tue, 29 Mar 2022 13:56:09 -0400 [thread overview]
Message-ID: <YkNIOS5E7gSH1cOk@vapier> (raw)
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2022-03-29 17:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 17:56 Mike Frysinger [this message]
2022-03-29 18:26 ` [gentoo-project] utilizing GH functionality that Gentoo infra does not provide 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ć
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=YkNIOS5E7gSH1cOk@vapier \
--to=vapier@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