public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris White <chriswhite@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Intent to help with #gentoo-dev voicing issues
Date: Wed, 15 Jun 2005 14:05:21 +0900	[thread overview]
Message-ID: <20050615140521.663e2a6f@localhost> (raw)
In-Reply-To: <42A77DF0.3030200@comcast.net>

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

> >>might I suggest not kicking #gentoo-dev visitors who ask for voice to
> >>speak to the devs without a 'rtfm & go get a gentoo job' smokescreen ?

My intentions in this email were regarding the above worries about things.  I plan to create somewhat of a consistant contact point between irc users that want a voice in dev.  If anyone has disagreements, I'll be happy to hear them out and hopefully address them.  My plan of interaction is as follows:

====
Plan
====

if you want a voice in #gentoo-dev, please ask me
if I'm not active, send me an email to this address letting me know what it is you'd like to discuss in dev

if you feel that I have handled the situation properly regarding your voicing, please send an email to dev-relations and I'll be happy to work things out.

Also if you send me an email, please put [gentoo-dev voicing request] in the topic, as well as your irc name and timezone for contact purposes.

I'll be leaving for work for about 8 hours from the time of this email, so don't expect too much of an immediate response.

Chris White

[-- Attachment #2: Type: application/pgp-signature, Size: 200 bytes --]

  parent reply	other threads:[~2005-06-14 20:37 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08 23:23 [gentoo-dev] a #g-d first impression might represent process and metastructure Jim Northrup
2005-06-09  0:14 ` Corey Shields
2005-06-09  0:18 ` Daniel Drake
2005-06-09  0:19 ` Joshua Baergen
2005-06-09  1:19   ` Jim Northrup
2005-06-09  1:45     ` Stephen P. Becker
2005-06-09  3:41       ` Lance Albertson
2005-06-09  8:30       ` Paul Waring
2005-06-11  3:19     ` Daniel Goller
2005-06-15 22:58       ` [gentoo-dev] a #g-d first impression about voip (semi-technical) Jim Northrup
2005-06-09  0:32 ` [gentoo-dev] a #g-d first impression might represent process and metastructure Mike Frysinger
2005-06-09 12:28 ` Luca Barbato
2005-06-15  5:05 ` Chris White [this message]
2005-06-14 20:38   ` [gentoo-dev] Intent to help with #gentoo-dev voicing issues Jan Kundrát
2005-06-15  8:56     ` Thierry Carrez
2005-06-15  9:01       ` [OT] " Andrej Kacian
2005-06-15 11:48         ` Thierry Carrez
2005-06-15  9:19     ` Luca Barbato
2005-06-15 14:01       ` Jan Kundrát
2005-06-14 20:41   ` Jonathan Smith
2005-06-14 21:00     ` Joshua Baergen
2005-06-14 21:02   ` Marius Mauch
2005-06-14 21:28     ` Donnie Berkholz
2005-06-15  9:21     ` Paul de Vrieze
2005-06-15  9:29       ` Andrej Kacian
2005-06-15  9:54         ` Paul de Vrieze
2005-06-15 10:03           ` Andrej Kacian
2005-06-15 12:09             ` Paul de Vrieze
2005-06-15 10:03         ` Jason Stubbs
2005-06-15 10:17           ` Andrej Kacian
2005-06-15 15:08             ` Marius Mauch
2005-06-15 19:09               ` Paul de Vrieze

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=20050615140521.663e2a6f@localhost \
    --to=chriswhite@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