From: Rob Cakebread <pythonhead@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New GLEP draft: Status of forum moderators in the Gentoo project
Date: Fri, 17 Jun 2005 15:40:25 -0700 [thread overview]
Message-ID: <42B35159.3090507@gentoo.org> (raw)
In-Reply-To: <20050617213818.GB14246@xover.htu.tuwien.ac.at>
Haas Wernfried wrote:
>
> Theoretically the trustees can decide to do whatever they want with
> the forums. They probably won't, but if anyone else who may be
> affected by their decisions is allowed to vote, why shouldn't we?
> The metastructure poll is affecting the forums in terms of us not even
> knowing where we fit into the metastructure even though f.g.o is in
> the offial domain gentoo.org.
> Becoming developer^wstaff should give us the right to vote. Since
> every other developer, infra staff, docs-writer or other person
> contributing time to gentoo as part of an official project, this
> should would be fair enough imho.
>
Ok, I'll buy that. This part wasn't clear to me:
"Recent events such as the election of trustees or the new metastructure
poll are effectively affecting the forums"
What you explained above is a lot clearer now, thanks.
--
Rob Cakebread
Gentoo Linux Developer
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x96BA679B
Key fingerprint = 5E1A 57A0 0FA6 939D 3258 8369 81C5 A17B 96BA 679B
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-06-17 22:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 18:44 [gentoo-dev] New GLEP draft: Status of forum moderators in the Gentoo project Christian Hartmann
2005-06-17 20:24 ` Jan Kundrát
2005-06-17 20:27 ` Jonathan Smith
2005-06-17 21:13 ` Haas Wernfried
2005-06-17 20:29 ` Rob Cakebread
2005-06-17 21:38 ` Haas Wernfried
2005-06-17 22:40 ` Rob Cakebread [this message]
2005-06-18 1:15 ` Roy Marples
2005-06-18 8:32 ` Haas Wernfried
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=42B35159.3090507@gentoo.org \
--to=pythonhead@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