From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Email subdomain
Date: Sat, 19 Nov 2005 01:39:58 -0700 [thread overview]
Message-ID: <pan.2005.11.19.08.39.57.23908@cox.net> (raw)
In-Reply-To: 200511182018.24457.cshields@gentoo.org
Corey Shields posted <200511182018.24457.cshields@gentoo.org>, excerpted
below, on Fri, 18 Nov 2005 20:18:24 -0800:
> On Friday 18 November 2005 08:02 pm, George Prowse wrote:
>> Of course, by being restrictive to the people who wish to help long-term
>> that is the greatest benefit to gentoo. If the @g.o email addresses are a
>> problem then the subdomain @staff.g.o has been suggested. The staff
>> subdomain would contain almost all relevant other domains. If in the
>> unlikely event that somone proposes a subdomain to gentoo that couldn't be
>> considered 'staff' or 'developer' then that can be considered at a later
>> date.
>
> I would consider such a silly proposal as the staff.gentoo.org subdomain
> addresses as "unlikely", so I'm just trying to think ahead..
OK, just picking the end of a random stair-step to tack on my viewpoint
and a bit of a summary from that viewpoint.
1) From what I've read, the idea of "staff" is a settled question. Infra
and other "staff" have @gentoo.org addresses and that's not up for debate.
It will continue to be that way.
2) The debate at the first council meeting reflected some concern about
AT/HTs getting "normal" @gentoo.org addresses, because a level of
commitment and discernment hasn't yet been fully proven.
3) That was resolved with the subdomain idea, which has now passed the
council (regardless of the circumstances and nil chance of something
similar happening again).
4) The problem is that the subdomain hasn't been specified, as there
wasn't really time to hash that out, so now we are doing that. Note,
however, that the decision that it /will/ be a subdomain has already been
made (unless someone's demanding that it be revoked, and I don't read the
discussion as getting to that point, yet).
5) Whatever the issue with staff vs. developers, that's a different, and
as mentioned in (1) basically settled issue, for better or for worse. The
idea here is that AT/HTs aren't even at the level of regular "staff", so
again, it's a different issue.
6) What AT/HTs are, as someone mentioned, are "gold star" users, if we
want to call them that. They are recognized as being quite useful to the
arch/herd, and as potential devs sometime in the future, should they wish
to pursue it and things work out, but there's a hesitance to give them
the full blessing yet, because they haven't proven themselves yet (and
regardless, some don't want it yet, or possibly ever).
7) Of course, "gold star" seems a bit childish, which I get the feeling
was the reason it was chosen, to drive home the viewpoint of the poster
that the whole idea IS childish. (Never-the-less, there's perhaps an
"adult" version of the same thing, see my proposal below.)
8) Infra has expressed reluctance, and asks the question if we accept this
one, where might it end? Legitimate question, but AFAICT, the question is
no longer whether this is a good idea or not as it's already been decided
to go ahead, but rather one of implementation, once the subdomain is
settled upon.
Now my thoughts, as one intending to become an AT at some point
and maybe, over an extended period, become a dev. (Yes, I'm sure Homer's
getting impatient with me, but what can I say, but my style is slow and
steady, but I'm not about to go elsewhere, either, so...)
a) I don't care one way or the other about a Gentoo address. As someone
else said, I've got enough addresses already. However, from what I've
read into the various discussions, the one's pushing for this, as the ones
pushing AT in the first place, have found that a gentoo.org label could at
times lessen the confusion. The subdomain would clarify things both from
the not-developer side, and from the recognized tester side, allowing new
ATs and devs to track the status on sight, with easy verification if
necessary. Thus, from my viewpoint, as received, this would seem to be a
convenience for the devs (including "staff") as much as for the AT/HTs.
b) With particularly points (3), (6) and (8) in mind, viewed thru the
filter of (7), it would appear to me that the best solution at this point
would be something denoting "junior" status, clearly lower than /either/
"staff" or "devs", as AT/HTs haven't yet proved themselves, something
that both staff and devs arguably have already done. At the same time, it
needs to be generic enough to be reused for other potential "junior" cases
in the future, thereby limiting the damage, from infra's perspective, to
the two domains (since the council already decided a subdomain was
necessary, just not which one, so it's really too late to argue that,
unless someone wants to do another GLEP recinding this one, with all the
politics /that/ would mean, just not a good idea IMO).
c) That lays out the requirements (and discussion to this point) as I see
them (and it). Assuming I'm viewing things correctly, then, the question
now becomes "What term clearly denotes junior status, without sounding
childish?" Put another way, "What's the generally accepted "adult"
term for student or trainee or junior member or "gold star earner"?
d) The best answer I can come up with is "intern", therefore,
"@intern.gentoo.org" (or @internee.gentoo.org, or...). AFAIK, that's
non-demeaning, yet clearly denotes the position as a one expected to do a
/lot/ of work, but still under serious supervision and without the
authority to make any heavy decisions without going thru someone else
first.
This proposal is of course recognizing that I might at some point have
such and address myself... I'd be comfortable with it -- actually more so
that with a full gentoo address, until such time (if ever) that I become
a full dev, of course.
Thoughts? Strong disagreements? Agreement? Points I overlooked? A
better suggestion? Go to it!
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-19 8:44 UTC|newest]
Thread overview: 143+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 17:09 [gentoo-dev] Email subdomain Homer Parker
2005-11-18 17:32 ` Henrik Brix Andersen
2005-11-18 22:01 ` Curtis Napier
2005-11-18 22:08 ` Homer Parker
2005-11-18 22:14 ` Ciaran McCreesh
2005-11-18 22:44 ` Curtis Napier
2005-11-18 22:55 ` Ciaran McCreesh
2005-11-18 23:18 ` Scott Stoddard
2005-11-18 23:21 ` Ciaran McCreesh
2005-11-19 15:43 ` Sune Kloppenborg Jeppesen
2005-11-18 23:29 ` Kurt Lieber
2005-11-18 23:34 ` Re[2]: " Jakub Moc
2005-11-21 10:15 ` Paul de Vrieze
2005-11-18 23:40 ` Luca Barbato
2005-11-18 23:46 ` Lance Albertson
2005-11-19 0:54 ` Grant Goodyear
2005-11-19 1:19 ` Luis F. Araujo
2005-11-19 1:36 ` George Prowse
2005-11-19 1:52 ` Lance Albertson
2005-11-19 4:22 ` Corey Shields
2005-11-19 4:31 ` Lance Albertson
2005-11-19 4:42 ` Corey Shields
2005-11-19 4:47 ` Dan Meltzer
2005-11-19 15:20 ` Grant Goodyear
2005-11-19 16:46 ` Thierry Carrez
2005-11-19 17:20 ` Corey Shields
2005-11-19 17:52 ` Corey Shields
2005-11-19 17:25 ` Lance Albertson
2005-11-19 17:49 ` Thierry Carrez
2005-11-19 18:24 ` Lance Albertson
2005-11-19 18:32 ` Lance Albertson
2005-11-19 18:05 ` Matti Bickel
2005-11-19 21:05 ` Danny van Dyk
2005-11-19 21:20 ` Lance Albertson
2005-11-19 22:19 ` Brian Harring
2005-11-19 22:46 ` Re[2]: " Jakub Moc
2005-11-19 22:46 ` Lance Albertson
2005-11-19 23:38 ` Brian Harring
2005-11-20 0:05 ` Lance Albertson
2005-11-20 0:52 ` Brian Harring
2005-11-19 23:06 ` Corey Shields
2005-11-20 0:09 ` Brian Harring
2005-11-20 0:31 ` Corey Shields
2005-11-19 22:17 ` Corey Shields
2005-11-23 0:52 ` Danny van Dyk
2005-11-18 23:47 ` Stuart Herbert
2005-11-18 23:47 ` Scott Stoddard
2005-11-19 0:02 ` Curtis Napier
2005-11-19 0:07 ` Homer Parker
2005-11-19 0:17 ` Re[2]: " Jakub Moc
2005-11-19 0:22 ` Kurt Lieber
2005-11-19 0:42 ` Grant Goodyear
2005-11-18 23:58 ` Grant Goodyear
2005-11-19 0:07 ` Re[2]: " Jakub Moc
2005-11-19 0:38 ` Grant Goodyear
2005-11-19 1:13 ` Luis F. Araujo
2005-11-19 1:25 ` Ciaran McCreesh
2005-11-19 1:55 ` Lance Albertson
2005-11-19 2:03 ` Scott Stoddard
2005-11-19 2:07 ` Ciaran McCreesh
2005-11-19 2:17 ` Dan Meltzer
2005-11-19 16:21 ` Tres Melton
2005-11-19 2:27 ` Re[2]: " Jakub Moc
2005-11-19 2:49 ` Ciaran McCreesh
2005-11-19 2:59 ` Re[2]: " Jakub Moc
2005-11-19 3:13 ` Ciaran McCreesh
2005-11-19 4:30 ` Stephen P. Becker
2005-11-19 8:11 ` Re[2]: " Jakub Moc
2005-11-19 14:33 ` Grant Goodyear
2005-11-19 3:01 ` Luis F. Araujo
2005-11-19 2:15 ` Re[2]: " Jakub Moc
2005-11-19 21:34 ` Corey Shields
2005-11-19 2:53 ` Ciaran McCreesh
2005-11-19 3:01 ` George Prowse
2005-11-19 3:16 ` Corey Shields
2005-11-19 3:40 ` George Prowse
2005-11-19 3:45 ` Corey Shields
2005-11-19 4:02 ` George Prowse
2005-11-19 4:18 ` Corey Shields
2005-11-19 8:39 ` Duncan [this message]
2005-11-19 9:23 ` [gentoo-dev] " Jason Stubbs
2005-11-19 23:46 ` Mike Frysinger
2005-11-20 0:13 ` Luis Medinas
2005-11-20 1:45 ` Jason Stubbs
2005-11-19 3:09 ` [gentoo-dev] " Corey Shields
2005-11-19 3:23 ` Ciaran McCreesh
2005-11-19 3:35 ` Corey Shields
2005-11-22 23:06 ` Marius Mauch
2005-11-19 9:31 ` Thierry Carrez
2005-11-19 9:46 ` Ciaran McCreesh
2005-11-19 11:00 ` Thierry Carrez
2005-11-19 11:07 ` Ciaran McCreesh
2005-11-19 16:06 ` Carsten Lohrke
2005-11-19 9:55 ` Re[2]: " Jakub Moc
2005-11-19 11:09 ` Thierry Carrez
2005-11-19 11:24 ` Ciaran McCreesh
2005-11-19 11:48 ` Jason Stubbs
2005-11-19 13:57 ` [gentoo-dev] Council Responsibilities (was: Email subdomain) Kurt Lieber
2005-11-19 14:23 ` Kurt Lieber
2005-11-19 1:09 ` [gentoo-dev] Email subdomain Luis F. Araujo
2005-11-19 5:33 ` Mike Frysinger
2005-11-19 5:54 ` Kurt Lieber
2005-11-19 7:10 ` Mike Frysinger
2005-11-19 19:48 ` Sven Vermeulen
2005-11-19 21:50 ` Scott Stoddard
2005-11-19 21:57 ` George Prowse
2005-11-19 22:08 ` George Prowse
2005-11-20 14:08 ` Ciaran McCreesh
2005-11-19 21:59 ` Mike Cvet
2005-11-19 22:01 ` Lares Moreau
2005-11-19 22:18 ` Patrick McLean
2005-11-19 22:29 ` Corey Shields
2005-11-19 22:27 ` Tres Melton
2005-11-19 22:40 ` Brian Harring
2005-11-19 23:07 ` Corey Shields
2005-11-19 23:45 ` Stuart Herbert
2005-11-19 22:32 ` Ben Skeggs
2005-11-22 23:19 ` Marius Mauch
2005-11-22 23:56 ` Lance Albertson
2005-11-23 15:38 ` [gentoo-dev] R/O CVS access and its purpose for ATs (was Email subdomain) Daniel Ostrow
2005-11-23 16:04 ` Kurt Lieber
2005-11-23 16:30 ` Lance Albertson
2005-11-24 14:46 ` George Prowse
2005-11-24 16:31 ` Lance Albertson
2005-11-18 19:31 ` [gentoo-dev] Email subdomain Wernfried Haas
2005-11-18 20:01 ` George Prowse
2005-11-18 21:06 ` Max
2005-11-18 22:17 ` Olivier Crete
2005-11-19 5:32 ` Mike Frysinger
2005-11-19 16:16 ` Lares Moreau
2005-11-19 15:51 ` Sune Kloppenborg Jeppesen
2005-11-19 16:38 ` Brian Harring
2005-11-19 16:46 ` Lares Moreau
2005-11-21 10:19 ` Paul de Vrieze
2005-11-22 23:26 ` Marius Mauch
2005-11-23 10:39 ` [gentoo-dev] Possible solution: email subdomain Duncan
2005-11-23 14:40 ` Marius Mauch
2005-11-23 18:47 ` [gentoo-dev] " Duncan
2005-11-23 19:07 ` Dan Meltzer
2005-11-23 19:34 ` Re[2]: " Jakub Moc
2005-11-23 19:47 ` Dan Meltzer
2005-11-23 22:28 ` Kurt Lieber
2005-11-23 23:07 ` Duncan
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=pan.2005.11.19.08.39.57.23908@cox.net \
--to=1i5t5.duncan@cox.net \
--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