public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Maciej Barć" <xgqt@gentoo.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: 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 18:00:42 +0200	[thread overview]
Message-ID: <f989e0ac-3435-402f-817c-2862af588750@gentoo.org> (raw)
In-Reply-To: <ubk5plecf@gentoo.org>


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

> I agree, but such documentation doesn't belong in an ebuild repository,
> but should be in a dedicated location like the Devmanual or the wiki.

 From our workflow and policy standpoint - yes; but to conform how it is 
mostly done in git forges like github/gitlab/codeberg etc this is also 
documented in LICENSE or COPYRIGHT file.
(Offotopic: though I use a dedicated dir called "Copyright" to put all 
legal info there for my own priovate repos.)

W dniu 1.05.2024 o 17:52, Ulrich Mueller pisze:
>>>>>> On Wed, 01 May 2024, Maciej Barć wrote:
> 
>>>> Also no license link. Afaik all contribs are under GPL-2.
> 
>>> That's not entirely correct. The files in the licenses/ directory
>>> aren't, and patches in packages' files/ dirs generally follow the
>>> license of their upstream project.
> 
>> See, so it would help to have a doc that talks about the
>> irregularities.
> 
> I agree, but such documentation doesn't belong in an ebuild repository,
> but should be in a dedicated location like the Devmanual or the wiki.
> 
> Ulrich

-- 
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 16:00 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ć
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ć [this message]
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=f989e0ac-3435-402f-817c-2862af588750@gentoo.org \
    --to=xgqt@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=ionen@gentoo.org \
    --cc=mgorny@gentoo.org \
    --cc=ulm@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