public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Suggestion to ask devs to change their bugzilla name when becoming "devaway"
Date: Thu, 10 Jun 2010 19:07:53 +0200	[thread overview]
Message-ID: <1276189673.15899.8.camel@localhost.localdomain> (raw)

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

Hello

Currently, we only need to set a proper message in ~/.away (as talked in
http://www.gentoo.org/proj/en/devrel/roll-call/devaway.xml ) when
becoming "devaway". The problem is that a lot of our users don't know
about that devaway list and, then, they will still open bug reports and
complaint when their reports get stalled due maintainer not being
available. 

My suggestion (until http://bugs.gentoo.org/show_bug.cgi?id=256934 is
solved) is to add a new step to "how to use the Devaway System"
instructions asking people to also change their bugzilla name appending
"(Devaway)", for example: 

"Pacho Ramos" would be changed to "Pacho Ramos (Deavaway)"

Then, people could simply search "devaway" in google and would get
proper information (gentoo devway page is the first shown)

Thanks

[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2010-06-10 17:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10 17:07 Pacho Ramos [this message]
2010-06-10 18:23 ` [gentoo-dev] Suggestion to ask devs to change their bugzilla name when becoming "devaway" Joe Peterson
2010-06-10 21:14   ` Pacho Ramos
2010-06-13  2:54     ` Mike Frysinger
2010-06-10 22:38 ` Christian Ruppert
2010-06-11  6:44   ` Pacho Ramos

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=1276189673.15899.8.camel@localhost.localdomain \
    --to=pacho@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