From: Chris Richards <gizmo@giz-works.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Lastrite: lince and slmodem
Date: Fri, 04 Feb 2011 17:38:58 -0600 [thread overview]
Message-ID: <4D4C8E12.2040808@giz-works.com> (raw)
In-Reply-To: <1296861883.15409.38.camel@raven.home.flameeyes.eu>
On 02/04/2011 05:24 PM, Diego Elio Pettenò wrote:
> This said, I'd suggest users and developers alike to add themselves (or
> ask to be added) to the metadata.xml files for packages requiring
> specific hardware support, so that even if one maintainer ends up not
> being active, we have a list of people who can actually tell us whether
> a given package works or not.
>
> And don't simply avoid doing so because there is someone else on that
> list already; we don't have a limit of one, two or three people listed
> in metadata.xml. The more people we know are ready to test a given
> package on actual hardware, the better (and you can be listed as "just a
> tester" after all).
What's true of developers is also true of users; a user may add
themselves to the list, forget they are on it, and a year from now be
asked to test something they no longer have hardware for.
Not saying that this isn't worth doing, merely pointing out that we may
discover that we don't have anyone to test even WITH the list of willing
users.
Later,
Chris
prev parent reply other threads:[~2011-02-04 23:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 19:09 [gentoo-dev] Lastrite: lince and slmodem Samuli Suominen
2011-02-01 20:11 ` Antoni Grzymala
2011-02-01 21:08 ` Matt Turner
2011-02-01 22:30 ` Samuli Suominen
2011-02-02 1:33 ` Matt Turner
2011-02-02 2:05 ` Jeremy Olexa
2011-02-02 7:41 ` Mike Frysinger
2011-02-04 23:24 ` [gentoo-dev] " Diego Elio Pettenò
2011-02-04 23:38 ` Chris Richards [this message]
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=4D4C8E12.2040808@giz-works.com \
--to=gizmo@giz-works.com \
--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