public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Usefulness of HOMEPAGE=https://www.gentoo.org
Date: Wed, 04 Dec 2019 13:36:07 +0100	[thread overview]
Message-ID: <0ebb1850c54ab69714e4f5e3525e8a40c74cb519.camel@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1809 bytes --]

Hi,

Many of Gentoo-originating packages are listing the main Gentoo site
as HOMEPAGE.  In my opinion, this is suboptimal (not to say 'useless').

I can think of a few uses for HOMEPAGE:

1. providing additional information about the package (before the user
chooses it),

2. providing easy access to (additional) documentation,

3. providing easy access to package sources,

4. providing easy access to bug reporting,

5. providing easy access to downloads.

A good HOMEPAGE is dedicated to the package in question, and makes it
easy to find all the stuff (and all other stuff the user might need).
The more effort user needs to put into finding what he needs, the worse
HOMEPAGE is.

Now, if I consider gentoo.org as a HOMEPAGE for ~90 packages it
currently is, it's horribly bad.  I suppose that in some cases authors
meant to indicate that Gentoo is the package's upstream.  However, by
going to the main Gentoo site, it's *very hard* to find anything about
the package in question.

Just please select a totally random package from those listing
gentoo.org as HOMEPAGE, then go to gentoo.org and try to find either
of the points listed above.  If you click 'Downloads', you're certainly
not going to find anything relevant.  Through 'Support', you may
eventually find that tiny Bugzilla button at the bottom... and then try
to find the correct Product.  You may also find gitweb link somewhere,
and try to see if the project has a repo there.  Or maybe it's somewhere
else, or maybe it existed on somebody's devspace once.

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.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 12:36 Michał Górny [this message]
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
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=0ebb1850c54ab69714e4f5e3525e8a40c74cb519.camel@gentoo.org \
    --to=mgorny@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