From: "Jorge Manuel B. S. Vicetto" <jmbsvicetto@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Should DevRel members be in Council?
Date: Thu, 18 Aug 2011 00:46:44 +0000 [thread overview]
Message-ID: <4E4C60F4.9020108@gentoo.org> (raw)
In-Reply-To: <CAGfcS_=1QuDhj-Zvr0zC5y8QnzpM45hRaM3cwAyuaR4+_VRArg@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 14-08-2011 14:52, Rich Freeman wrote:
<snip>
Just to clarify the above statement, everyone that joins gentoo and gets
the @gentoo.org address is a Gentoo *developer*. Some developers have
gentoo-x86 access (tree access), others might do documentation work,
moderate the forums, work with infrastructure or something else, but
even though it's easier to call them *staffers*, they are *developers* -
they just may lack the gentoo-x86 commit access.
Then we have everyone else that has made a commitment to Gentoo, albeit
with a smaller scale, and that has got the AT/HT "stamp" and everyone
else that may not have an official role but help make this a better
distribution and community every day.
- --
Regards,
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
Gentoo- forums / Userrel / Devrel / KDE / Elections / RelEng
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJOTGDsAAoJEC8ZTXQF1qEP76AQAJRDhooZSLHdgGIm4xHPvsJd
YAlNrM4iEeV1uA+rZHQRxmxdDFsIbqM2CDPhMFPRAycDjNskWHuvXTJORZZKsVae
Ddjbw5Hijj3DLNrLUt50og1cMthxNDczVSCOFPyI/ukZNXa0v3pVdykJAVt+3mBE
6IcQDBk0mZhKTtvu6uzBMueVVpwJ6Bm1K7UREGP+eog/rBX2ZqJbYuH9bfbGyiKb
KnwVGLHbOZcCis8rZqO5WGeMKdQLRu6UvdKbiGu0WBkIfq+MaFVO5VOZwnRblcV7
I9rwy9HRo4+8RFLOEQAKOT0alvuz3Y9oRCCycWDKwaBi0S/w14MGhett7HHk5lTp
H3So618KsQJximESlUIMmqmbqBinPOlR0R64gy4niRLoaPvavEAZKtK4MaUrlg+f
XArThJAArN6Cy30CkJXupEKw7xY8u8WPgsVq4i7Xtkb9N+WOysBfPQAzIA2YoUAZ
TrZDogGv67E7VUzVU76/y33ExTYbRTeWhzzTXXXQ3Bceotvho77ZmrMZw1vhh8q2
ncdjklivtPnYpq3XEZKkgylWyhFM4HoaatXyAboHm6CJ/4mlrqAyIKy4EvHT/kL6
ia6/pMJyHQOuQeypHa/oXIZ3ilekOZZQ1Fia2jfkyOjQyrajUP2pUeMfkz9xvPBH
zgltFvdp7jGsl7dZvqbk
=+LBS
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-08-18 0:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-14 11:12 [gentoo-project] Should DevRel members be in Council? Markos Chandras
2011-08-14 11:25 ` Rich Freeman
2011-08-14 14:42 ` Roy Bamford
2011-08-14 14:52 ` Rich Freeman
2011-08-14 16:24 ` Roy Bamford
2011-08-18 0:46 ` Jorge Manuel B. S. Vicetto [this message]
2011-08-14 19:01 ` Mike Frysinger
2011-08-14 11:27 ` Fabian Groffen
2011-08-14 11:31 ` Markos Chandras
2011-08-14 11:50 ` Rich Freeman
2011-08-14 11:38 ` Rich Freeman
2011-08-14 12:19 ` Thomas Sachau
2011-08-14 12:26 ` Markos Chandras
2011-08-14 13:14 ` Thomas Sachau
2011-08-14 13:42 ` Markos Chandras
2011-08-14 14:05 ` Petteri Räty
2011-08-14 14:11 ` Markos Chandras
2011-08-14 14:42 ` Petteri Räty
2011-08-14 19:01 ` Mike Frysinger
2011-08-15 2:19 ` Samuli Suominen
2011-08-15 2:46 ` Rich Freeman
2011-08-18 1:25 ` Jorge Manuel B. S. Vicetto
2011-08-16 18:28 ` William Hubbs
2011-08-16 19:17 ` Rich Freeman
2011-08-16 20:46 ` Donnie Berkholz
2011-08-17 2:46 ` Mike Frysinger
2011-08-16 19:32 ` Roy Bamford
2011-08-18 1:09 ` Jorge Manuel B. S. Vicetto
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=4E4C60F4.9020108@gentoo.org \
--to=jmbsvicetto@gentoo.org \
--cc=gentoo-project@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