public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joonas Niilola <juippis@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Usefulness of HOMEPAGE=https://www.gentoo.org
Date: Wed, 4 Dec 2019 21:58:45 +0200	[thread overview]
Message-ID: <f019b0ec-b925-627c-28b6-5d3783ddbfef@gentoo.org> (raw)
In-Reply-To: <882242c53652bb5844fe0b315f384c9bbf5354a7.camel@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 1492 bytes --]


On 12/4/19 7:26 PM, Michał Górny wrote:
> On Wed, 2019-12-04 at 17:24 +0200, Joonas Niilola wrote:
>> On 12/4/19 5:21 PM, Kent Fredric wrote:
>>> On Wed, 04 Dec 2019 13:36:07 +0100
>>> Michał Górny <mgorny@gentoo.org> wrote:
>>>
>>>> My point is: gentoo.org as a HOMEPAGE sucks.  Please use something more
>>>> specific instead.  Even link to gitweb would be more helpful because it
>>>> would at least be relevant to the package in question.
>>> I agree so much I would support the addition of a QA check for this.
>>>
>> I take it you haven't checked the CI results lately? Reaction to that
>> probably spawned this ML thread.
>>
>> https://qa-reports.gentoo.org/output/gentoo-ci/output.html
> Actually, I've requested that check.  However, I didn't expect that many
> packages to be affected.
>
> Given that it's open season on me lately, and apparently people feel
> offended when bugs are reported for their packages, I've decided to
> start by trying to make people realize the problem globally first.

That's a nice initiatitve. Overall I feel like (global) future CI checks
should be discussed first, because they affect everyone who's
committing, and it feels weird starting to suddenly receive mails about
things you've pushed a hundred times before. As seen by the evergrowing
list of new warnings, people just start to ignore these new checks or
"fix it on next version bump", because knowledge wasn't there on a
previous one.

-- juippis



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

  reply	other threads:[~2019-12-04 19:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 12:36 [gentoo-dev] Usefulness of HOMEPAGE=https://www.gentoo.org Michał Górny
2019-12-04 12:44 ` [gentoo-dev] Re: HOMEPAGE and DESCRIPTION in ebuilds? (was: Usefulness of HOMEPAGE=https://www.gentoo.org) Miroslav Šulc
2019-12-04 13:11   ` Michał Górny
2019-12-04 15:18   ` Kent Fredric
2019-12-04 13:25 ` [gentoo-dev] Usefulness of HOMEPAGE=https://www.gentoo.org Michał Górny
2019-12-04 15:21 ` Kent Fredric
2019-12-04 15:24   ` Joonas Niilola
2019-12-04 15:47     ` Kent Fredric
2019-12-04 17:26     ` Michał Górny
2019-12-04 19:58       ` Joonas Niilola [this message]
2019-12-04 21:32       ` Alec Warner

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=f019b0ec-b925-627c-28b6-5d3783ddbfef@gentoo.org \
    --to=juippis@gentoo.org \
    --cc=gentoo-dev@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