| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Christel, |
| 5 |
In case you missed it. Intriguing idea. |
| 6 |
|
| 7 |
Regards, |
| 8 |
Ferris |
| 9 |
|
| 10 |
- -- |
| 11 |
Ferris McCormick (P44646, MI) <fmccor@g.o> |
| 12 |
Developer, Gentoo Linux (Devrel, Sparc) |
| 13 |
|
| 14 |
- ---------- Forwarded message ---------- |
| 15 |
Date: Sun, 9 Apr 2006 00:40:54 +0000 (UTC) |
| 16 |
From: S. Lockwood-Childs <wormo@g.o> |
| 17 |
Reply-To: gentoo-dev@l.g.o |
| 18 |
To: gentoo-dev@l.g.o |
| 19 |
Cc: Christopher O'Neill <chris.oneill@×××××.com> |
| 20 |
Subject: Re: [gentoo-dev] Re: Improving Gentoo User Relations (fwd) |
| 21 |
|
| 22 |
I apologize if this is a resend, but it seemed to me like the 1st attempt |
| 23 |
didn't get through (can't imagine why it would take longer than a couple |
| 24 |
of days to get to a gentoo-hosted mailing list from a gentoo-hosted mail |
| 25 |
account...) |
| 26 |
|
| 27 |
- ------------------ |
| 28 |
|
| 29 |
On Fri, 7 Apr 2006, Christopher O'Neill wrote: |
| 30 |
|
| 31 |
> As a Gentoo user, one thing that I'd very much like to see is improved |
| 32 |
> communication between the dev teams and the users. At the moment it |
| 33 |
> feels pretty much like I am in the dark as regarding to how we are |
| 34 |
> progressing on certain things. Let me pick some examples: |
| 35 |
|
| 36 |
I wonder if we could get an AT or dev to join userrel team as a liason for |
| 37 |
the express purpose of keeping users updated on progress |
| 38 |
|
| 39 |
* user has a question regarding current status in project XYZ |
| 40 |
* user sees a link regarding 'learn current status' on front page of |
| 41 |
gentoo.org |
| 42 |
* user reads this status page to see if the question has already |
| 43 |
been answered |
| 44 |
* user has a new question not addressed by existing info, and submits it via |
| 45 |
a form to the liason email account |
| 46 |
* user gets an auto-generated response indicating the request has been |
| 47 |
received (i.e. made it past the spam filter) and asking them not to re-submit |
| 48 |
questions as it can take time to research answers |
| 49 |
|
| 50 |
* status answer guy reads question and asks for clarification if needed |
| 51 |
* status answer guy either: |
| 52 |
* already knows answer from mailing lists or irc |
| 53 |
* searches through relevent mailing lists |
| 54 |
* asks on relevent irc channel |
| 55 |
* asks on a relevent mailing list |
| 56 |
* asks a relevent dev via email |
| 57 |
* status answer guy writes a brief update with relevent pointers and sends |
| 58 |
it to the relevent devs for approval (analagous to draft of GWN getting |
| 59 |
posted before published) |
| 60 |
* status answer guy posts the update (with any corrections) to the status |
| 61 |
web page and sends an email telling user(s) who asked this question |
| 62 |
that the status page got updated |
| 63 |
|
| 64 |
Suggested requirements for this position: |
| 65 |
* diplomatic and patient with both users and devs |
| 66 |
* not easily offended |
| 67 |
* broad interest in many areas of gentoo |
| 68 |
* already hangs out in irc and subscribes to many mailing lists (likely to |
| 69 |
know who to ask, or on what mailing list) |
| 70 |
* doesn't mind doing a little writing and is decent at it |
| 71 |
- -- |
| 72 |
gentoo-dev@g.o mailing list |
| 73 |
|
| 74 |
-----BEGIN PGP SIGNATURE----- |
| 75 |
Version: GnuPG v1.4.2.2-ecc0.1.6 (GNU/Linux) |
| 76 |
|
| 77 |
iD8DBQFEOHbiQa6M3+I///cRAh0sAJ4646i/JuKS/ev1LPV7x4z1+9hXDgCgk5+R |
| 78 |
V3c4ItlsyC4YoP2k0Ds0ZdI= |
| 79 |
=4UFO |
| 80 |
-----END PGP SIGNATURE----- |
| 81 |
-- |
| 82 |
gentoo-devrel@g.o mailing list |
Archives