public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Maciej Barć" <xgqt@gentoo.org>
To: gentoo-dev@lists.gentoo.org, "Michał Górny" <mgorny@gentoo.org>,
	"Ionen Wolkens" <ionen@gentoo.org>
Subject: Re: [gentoo-dev] [PATCH] .github: Add pull request template
Date: Wed, 1 May 2024 16:38:43 +0200	[thread overview]
Message-ID: <cd882143-c714-4770-a16a-5102c64a2f27@gentoo.org> (raw)
In-Reply-To: <ZjJRljufRtviIbM3@eversor>


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

Ionen, I think that regular contributors could skip this altogether. For 
example the person I'm mentoring I am sure would follow all requirements 
listed by mgorny and me (see my reply).

> On a side-note, I have nothing against having .github in the tree. Just
> saying given I know not everyone is happy with that.

I think we should push more into "conforming" to standard of online 
software forges. Reminder that we STILL do not have any form of a README 
file. Not even one that would say "Hey look at https://gentoo.org/". 
Also no license link. Afaik all contribs are under GPL-2.

W dniu 1.05.2024 o 16:28, Ionen Wolkens pisze:
> On Wed, May 01, 2024 at 03:32:21PM +0200, Michał Górny wrote:
>> The idea is to increase awareness of the AI policy, as well as other
>> rules, and to inform users before they submit a PR.
> 
> Bit mixed feelings about this given checkboxes feel like unnecessary
> churn for routine contributors and is semi-redundant with the
> Signed-off-by.
> 
> I think it's great for first-time/occasional contributors though.
> 
> Having a AI-specific checkbox does feel kind of overkill when it won't
> concern the majority of contributors, albeit given how how hard the whole
> thing is pushed lately and that we have no real way to verify beside the
> user being made aware of it and certifying it...
> 
> On a side-note, I have nothing against having .github in the tree. Just
> saying given I know not everyone is happy with that.

-- 
Have a great day!

~ Maciej XGQT Barć

https://wiki.gentoo.org/wiki/User:Xgqt
9B0A 4C5D 02A3 B43C 9D6F D6B1 14D7 4A1F 43A6 AC3C

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

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

  reply	other threads:[~2024-05-01 14:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-01 13:32 [gentoo-dev] [PATCH] .github: Add pull request template Michał Górny
2024-05-01 14:27 ` Maciej Barć
2024-05-01 14:47   ` Eli Schwartz
2024-05-01 15:02     ` Maciej Barć
2024-05-01 15:15       ` Eli Schwartz
2024-05-01 15:18         ` Maciej Barć
2024-05-01 14:59   ` Michał Górny
2024-05-01 15:14     ` Maciej Barć
2024-05-01 14:28 ` Ionen Wolkens
2024-05-01 14:38   ` Maciej Barć [this message]
2024-05-01 14:54     ` Eli Schwartz
2024-05-01 15:01     ` Ulrich Mueller
2024-05-01 15:05       ` Maciej Barć
2024-05-01 15:52         ` Ulrich Mueller
2024-05-01 16:00           ` Maciej Barć
2024-05-01 15:00   ` Michał Górny
2024-05-03  4:41   ` Sam James
2024-05-03  4:41 ` Sam James

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=cd882143-c714-4770-a16a-5102c64a2f27@gentoo.org \
    --to=xgqt@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=ionen@gentoo.org \
    --cc=mgorny@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