From: "Nathan L. Adams" <nadams@ieee.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ROX: maintainer-wanted and apps out of date
Date: Mon, 12 Sep 2005 20:20:04 -0400 [thread overview]
Message-ID: <43261B34.5020209@ieee.org> (raw)
In-Reply-To: <20050912202143.1c487a31@snowdrop.home>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ciaran McCreesh wrote:
> And as for taking it as a PISSOFF... We've had exactly one person do
> that so far. All the rest of the feedback we receive -- which is a heck
> of a lot -- is of the "thanks for the pointers, please could someone
> check this updated ebuild?" and occasionally "could you clarify $blah
> for me please?" variety.
My first inclination is to take "WONTFIX" as "PISSOFF", and I even read
the previous thread in question. :)
I humbly suggest adding a "REVIEWED" and/or "NEEDSWORK" keyword and
leaving the bug in the OPEN or ASSIGNED state.
But adding the comments (with pointers to more in-depth explanations) is
a great idea, especially if you present them in a cordial way:
Thanks for helping Gentoo! The ebuild you submitted isn't quite
ready, so here is what one needs to do to get it in the tree:
link1
link2
Thanks again!
Which is probably what you're doing already. :)
As for missing/AWOL developers, and for developer/user problem
resolution, I *think* devrel handles that:
http://www.gentoo.org/proj/en/devrel/
Nathan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDJhs02QTTR4CNEQARApZsAJ9+KRCAsawb5/fVD8FFpTO0d2TitACgmqH2
OI1jP3uv+/Ll7qHOawzqowo=
=VPCh
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-13 0:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 13:58 [gentoo-dev] ROX: maintainer-wanted and apps out of date Peter Hyman
2005-09-11 15:50 ` Maurice van der Pot
2005-09-11 16:42 ` Peter Hyman
2005-09-11 19:24 ` Maurice van der Pot
2005-09-11 21:02 ` Alin Nastac
2005-09-12 0:10 ` Aron Griffis
2005-09-12 7:04 ` Alin Nastac
2005-09-12 0:14 ` Peter Hyman
2005-09-12 0:25 ` Ciaran McCreesh
2005-09-12 0:38 ` Alec Warner
2005-09-12 11:55 ` Carsten Lohrke
2005-09-12 14:03 ` Chris Gianelloni
2005-09-12 14:26 ` Re[2]: " Jakub Moc
2005-09-12 14:28 ` Maurice van der Pot
2005-09-12 15:41 ` Peter Hyman
2005-09-12 16:12 ` Martin Schlemmer
2005-09-12 17:00 ` Peter Hyman
2005-09-12 17:12 ` Jan Kundrát
2005-09-12 17:25 ` Stephen P. Becker
2005-09-12 17:51 ` Chris Gianelloni
2005-09-12 17:03 ` Ciaran McCreesh
2005-09-12 17:32 ` Carsten Lohrke
2005-09-12 17:40 ` Ciaran McCreesh
2005-09-12 17:56 ` Re[2]: " Jakub Moc
2005-09-12 18:53 ` Carsten Lohrke
2005-09-12 19:21 ` Ciaran McCreesh
2005-09-13 0:20 ` Nathan L. Adams [this message]
2005-09-12 19:26 ` [gentoo-dev] " Dan Meltzer
2005-09-12 0:27 ` [gentoo-dev] " Stephen P. Becker
2005-09-12 0:36 ` Peter Hyman
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=43261B34.5020209@ieee.org \
--to=nadams@ieee.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