public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeroen Roovers <jer@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] new developers' keyword requests
Date: Thu, 19 May 2016 16:51:30 +0200	[thread overview]
Message-ID: <20160519165130.7e9bc385@wim.fritz.box> (raw)

Perhaps it's a good idea to add a section to the devmanual about adding
new keywords to packages.

Recruits in particular might benefit from some background on what
keywording means and when it should be done, especially before they
start maintaining packages and then realise their packages are so
beautiful that they positively *deserve* to have some random keywords
added. This is not productive.

The way it works is that users of
specific architectures find that a package works for them on their
systems (which have enough resources and have the correct interfaces for
that particular program to be used conveniently, and so on), and that
they then request that their architecture keyword be added. What
doesn't work is having a handful of keywords on a package that nobody
cares about who actually uses the architectures in question.

Since over the years the Random Keyword Requests happen a *lot* right
after recruitment, it might even be useful to ask about this in the
quizzes. (The answer: your time is better spent fixing actual bugs.
bumping versions, adding features and maintaining a stable branch,
rather than raising the architecture count for your packages for no
adequately explored reason.)


Kind regards,
     jer


             reply	other threads:[~2016-05-19 14:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-19 14:51 Jeroen Roovers [this message]
2016-05-19 15:00 ` [gentoo-dev] new developers' keyword requests Mike Gilbert
2016-05-20  1:36 ` Daniel Campbell
2016-05-20 12:38   ` Kristian Fiskerstrand
2016-05-20 13:11     ` Kristian Fiskerstrand
2016-05-20 13:34       ` M. J. Everitt
2016-05-20 13:20     ` Daniel Campbell
2016-05-20 14:00   ` Jeroen Roovers
2016-05-21  2:09     ` Ian Delaney
2016-05-21  2:35       ` Sam Jorna
2016-05-21  4:47   ` Matt Turner
2016-05-21  6:41     ` Daniel Campbell
2016-05-21  7:08     ` [gentoo-dev] " Duncan
2016-05-21  9:01     ` [gentoo-dev] " Jeroen Roovers

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=20160519165130.7e9bc385@wim.fritz.box \
    --to=jer@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