From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] PR Project Activity Issues
Date: Fri, 30 Jan 2009 22:20:27 -0800 [thread overview]
Message-ID: <20090131062027.GA7480@hermes> (raw)
In-Reply-To: <b41005390901270155i52ea7e4bhbcf119df0cbc4828@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1832 bytes --]
On 01:55 Tue 27 Jan , Alec Warner wrote:
> Getting Index2 live is I think a different operational issue (that
> changes to the website are very slow) and really has nothing to do
> with PR aside from them not nagging someone to commit it ;)
In this case, Xavier had it ready in early January, and I was blocking
on it for the last 2 weeks to write up an announcement.
> PR@ is a nghtmare of spam and what I'll term 'crap.' having real
> things marked as such with informative subjects would be useful.
> having some kind of rotation would be useful having some kind of vague
> 'we will read and respond within 3 days unless its a holiday' would be
> useful.
>
> Right now the expectations of pr@ are non-existent and apparently
> think the mail is read and answered quickly. In reality only Donnie
> reads it and replies; he has a busy as hell personal life and I'm
> surprised he manages to read it at all.
>
> So I would like to set expectations ;)
Yes, it would be a good idea to put expectations wherever people find
our contact info. Here's roughly what they are:
1. If it is a prewritten news item that needs editing, it will get a quick
response.
2. If it is news that is not accompanied by a draft of some sort, no
estimated response time. This point is where I think we have the biggest
opportunity for improvement.
3. If it is an additional vendor listing for CDs, no estimated response
time. These generally get batched and done at extended intervals.
4. If it is a user support request, no estimated response time.
Occasionally someone will respond to say that we don't do support at pr@
and point at appropriate places like forums, lists, IRC.
--
Thanks,
Donnie
Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-31 6:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 21:30 [gentoo-dev] PR Project Activity Issues AllenJB
2009-01-27 2:46 ` Jesus Rivero
2009-01-27 4:28 ` Douglas Anderson
2009-01-27 4:47 ` Alec Warner
2009-01-27 5:50 ` [gentoo-dev] " Ryan Hill
2009-01-27 6:21 ` Josh Saddler
2009-01-27 8:17 ` [gentoo-dev] " AllenJB
2009-01-27 9:55 ` Alec Warner
2009-01-27 11:38 ` Tobias Scherbaum
2009-01-31 6:20 ` Donnie Berkholz [this message]
2009-02-01 7:35 ` Alec Warner
2009-02-02 4:53 ` Donnie Berkholz
2009-01-27 6:07 ` Donnie Berkholz
2009-01-27 7:17 ` Ben de Groot
2009-01-27 7:51 ` Alec Warner
2009-01-27 11:08 ` Man Shankar
2009-01-27 16:38 ` Nathan Zachary
2009-01-27 8:42 ` AllenJB
2009-01-31 6:24 ` Donnie Berkholz
2009-01-30 12:02 ` djay
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=20090131062027.GA7480@hermes \
--to=dberkholz@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