[gentoo-project] Gentoo Code of Conduct

[gentoo-project] Gentoo Code of Conduct

[Tomáš Chvátal]

[-- Attachment #1.1: Type: text/plain, Size: 743 bytes --]

Hello guys,

after last bunch of mails and internal complains I decided it is time to do
something proactive.

So I give you revised Gentoo Code of Conduct.

The plan is to have this document and policies watched by all people and
violations to be reported on irc to devrel/userrel (there is plan to merge
those but that is for Jorge and Markos to sort out).

I would like to hear all kind of suggestions for wording in the document. I
tried my best but I suck at expressing myself so please do your best.

The plan is to have more friendly environment to bring back the fun instead
of all the flames and insults.

This document should be polished prior next council meeting here and then
discussed and voted upon in the meeting.

Cheers

Tom

[-- Attachment #1.2: Type: text/html, Size: 974 bytes --]

[-- Attachment #2: gentoo-coc.txt --]
[-- Type: text/plain, Size: 7072 bytes --]

Gentoo Code of Conduct 0.3

Preamble
--------

Gentoo is a distribution developed world-wide. We all collaborate to improve 
Gentoo and its usage.

We strive for a happy and friendly community that can embrace new ideas,
improve and foster collaboration among groups with different goals,
interests and needs.

The Code of Conduct governs how we behave in public or in private whenever the 
project will be judged by our actions. We expect it to be honored by everyone 
who represent the project officially or informally, claim affiliation with 
the project, or participate directly.

Questions about this document and its contents can be directed to the Gentoo 
council at council@gentoo.org.

Overview
--------

Basic social consents that our project works with are:

 - Be considerate
 - Be responsible
 - Be respectful
 - Be collaborative
 - Support others in the community and get support from them

Be considerate
--------------

As a contributor, ensure that you give full credit for the work of others and 
bear in mind how your changes affect others. It is also expected that you try 
to follow the development schedule and guidelines.

As a user, remember that contributors work hard on their part of the 
distribution and take great pride in it. If you are frustrated, your problems
are more likely to be resolved if you give accurate description and keep being
polite and behave in well-mannered way.

Any decission we make will affect users and colleagues, and we should consider 
them when making those decission.

Be responsible
--------------

We can all make mistakes; when we do, we take responsibility for them. If 
someone has been harmed or offended, we listen carefully and respectfully, and 
work to right the wrong.

Keep in mind that undoing one wrongdoing usually takes at least three
positive ones in the eyes of the harmed/offended person.

Be respectful
-------------

In order for the Gentoo community to stay healthy, its members must feel 
comfortable and accepted. Treating one another with respect is absolutely 
necessary for this. In a disagreement, in the first instance assume that people 
mean well.

We do not tolerate personal attacks, racism, sexism or any other form of 
discrimination. Disagreements are inevitable, from time to time, but respect
for the views of others will go a long way to winning respect for your own
view.

Respecting other people, their work, their contributions and assuming 
well-meaning motivation will make community members feel comfortable and safe 
and will result in motivation and productivity.

We expect members of our community to be respectful when dealing with other 
contributors, users and communities. Remember that Gentoo is an international 
project and that you may be unaware of important aspects of other cultures.

Be collaborative
----------------

What we produce is a complex whole made of many parts, it is the sum of many 
dreams. Collaboration between teams that each have their own goal and vision is 
essential; for the whole to be more than the sum of its parts, each part must 
make an effort to understand the whole.

Collaboration reduces redundancy and improves the quality of our work. 
Internally and externally, we celebrate good collaboration. Wherever possible, 
we work closely with upstream projects and others in the free software 
community to coordinate our efforts. We prefer to work transparently and 
involve interested parties as early as possible.

It may not always be possible to reach consensus on the implementation of an 
idea, so don't feel obliged to achieve this before you begin. However, always 
ensure that you keep others informed of your work, and publish it in 
a way that allows outsiders to test, discuss and contribute to your efforts.

Contributors on every project come and go. When you leave or disengage from the 
project, in whole or in part, you should do so with pride about what you have 
achieved and by acting responsibly towards others who come after you to 
continue the project.

As a user, your feedback is important, as is its form. Poorly thought out 
comments can cause pain and the loss of motivation of other community members,
but considerate discussion of problems can bring positive results. An
encouraging word works wonders.

Support others in the community and get support from them
---------------------------------------------------------

If you witness others being attacked, think first about how you can offer them 
personal support. If you feel that the situation is beyond your ability to help 
individually, go privately to the victim and ask if some form of official 
intervention is needed. Similarly you should support anyone who appears to be 
in danger of burning out, either through work-related stress or personal 
problems.

When problems do arise, consider respectfully reminding those involved of our 
shared Code of Conduct as a first action.

Disagreements, both political and technical, happen all the time. Our community 
is no exception to the rule. The goal is not to avoid disagreements or 
differing views but to resolve them constructively.

Think deeply before turning a disagreement into a public dispute. If you do 
feel that you or your work is being attacked, take your time to breathe
through before writing heated replies.


Examples of inappropriate behavior
-----------------------------------

 - offensive verbal comments related to gender, sexual orientation, race, 
   cultural background or other personal characteristics
 - inappropriate jokes or insults
 - sexual or racial images in public accessible areas (git, mailing-list, irc 
   channels, ...)
 - intentional off-topic communication (flame-wars) starting

Consequences of such behaviour
------------------------------

Disciplinary action will be up to the descretion of the enforcers. What is a 
enforcer? An enforcer is an official charged with the duty of maintaining good 
order. Currently this responsibility falls to two existing Gentoo projects: 
DevRel and UserRel.

If you perceive a breach of the Code of Conduct guidelines, let the appropriate 
enforcers know. Though they will also be watching many of the public mediums for 
any problems, they can not be expected to catch everything. If the offender is a 
Gentoo developer, contact devrel@g.o, otherwise contact userrel@g.o.

The enforcers will attempt to resolve the problem by talking to involved parties, 
potentially issuing warnings if appropriate. If the problem repeats itself, 
there are various options open to the enforcers, including temporary or permanent 
suspension of a person's ability to post to mailing lists, removal of Bugzilla 
access, or in more severe cases suspension of developer privileges.

If discplinary measures are taken and the affected person wishes to appeal, 
it should be addressed to the Gentoo Council via email at council@g.o. To
prevent conflicts of interest, Council members may not perform the duties of
an enforcer.


--
Based on KDE, openSUSE, Ubuntu and former Gentoo CoC.

Released under CC-SA 3.0

Re: [gentoo-project] Gentoo Code of Conduct

[Rich Freeman]

On Fri, May 24, 2013 at 7:46 AM, Tomáš Chvátal <scarabeus@gentoo.org> wrote:
> I would like to hear all kind of suggestions for wording in the document. I
> tried my best but I suck at expressing myself so please do your best.

I'd recommend dropping the last sentence about council members not
being enforcers, because this is not really a conflict of interest.
The council is the elected body in charge of non-legal aspects of the
community - devrel exists and serves at its pleasure.  If we can't
trust the council to act responsibly, then there is really nothing
that we can do to keep the project running well.

That said, I know that there has been back-and-forth on this in the
past.  If the council doesn't object to the wording I'll say nothing
further.

Rich

Re: [gentoo-project] Gentoo Code of Conduct

[Tomáš Chvátal]

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

2013/5/24 Rich Freeman <rich0@gentoo.org>

> On Fri, May 24, 2013 at 7:46 AM, Tomáš Chvátal <scarabeus@gentoo.org>
> wrote:
> > I would like to hear all kind of suggestions for wording in the
> document. I
> > tried my best but I suck at expressing myself so please do your best.
>
> I'd recommend dropping the last sentence about council members not
> being enforcers, because this is not really a conflict of interest.
> The council is the elected body in charge of non-legal aspects of the
> community - devrel exists and serves at its pleasure.  If we can't
> trust the council to act responsibly, then there is really nothing
> that we can do to keep the project running well.
>

Hi,

Thats a question, someone could correctly state that appealing mechanism
member should not be involved in the first level resolution.
Because this way it can be that you actually complain about decision of a
guy to the same guy.

Thats why I think that council should be taken out from making the first
decision. But it does not mean that they can't give out suggestions for
resolutions, they just should not be the one who effectively make it.

Cheers

Tom

[-- Attachment #2: Type: text/html, Size: 1733 bytes --]

Re: [gentoo-project] Gentoo Code of Conduct

[Rich Freeman]

On Fri, May 24, 2013 at 9:16 AM, Tomáš Chvátal <scarabeus@gentoo.org> wrote:
> Thats a question, someone could correctly state that appealing mechanism
> member should not be involved in the first level resolution.

They could state that.  There isn't anything "correct" or "incorrect"
about that statement as it is a statement of values, not fact.

The fact is that if the council is the judge then you don't have
anyone to appeal it to.  Whether that is a good thing or a bad thing
is a matter of opinion.  I'm of the opinion that it is neither good or
bad.  If the council doesn't like you they can just appoint an
enforcer who will bring charges against you and then uphold them on
appeal.  If the community can't elect a decent group to govern it from
within its ranks, then it is basically doomed no matter what the
policies are.

> Because this way it can be that you actually complain about decision of a
> guy to the same guy.

Yup.  I agree that this would be a consequence of changing the policy.
 I think a unitary system of government makes sense for organizations
smaller than a few million people, and a unitary government is one in
which the topmost authority has absolute authority (though they can be
elected, and can be a board).  That is how most companies and even how
most democracies work (the US being a noteworthy exception).  The
routine process may be to appeal to your local zoning board before
going to parliament, but if for whatever reason your parliament was
interested they could tell the zoning board to take a hike before they
even make a ruling.  In general this doesn't happen because
responsible boards don't micro-manage, and I fully support that as
well.

I'm not a fan of having confused lines of authority where everybody is
in charge and as a result things get deadlocked.  I'm all for having
delegated authority and collaboration, and I don't want the highest
authority to step in on every decision.  However, I don't think the
authority of the council should be limited in any way as it concerns
the governance of the non-legal aspects of Gentoo, except that they
stand for election.  That is their mandate.

But, others feel differently, and as I said if the council doesn't
object to curtailing their authority, then I'll defer to them.

Rich

Re: [gentoo-project] Gentoo Code of Conduct

[Markos Chandras]

On 24 May 2013 14:46, Rich Freeman <rich@thefreemanclan.net> wrote:
> On Fri, May 24, 2013 at 9:16 AM, Tomáš Chvátal <scarabeus@gentoo.org> wrote:
>
> I'm not a fan of having confused lines of authority where everybody is
> in charge and as a result things get deadlocked.  I'm all for having
> delegated authority and collaboration, and I don't want the highest
> authority to step in on every decision.  However, I don't think the
> authority of the council should be limited in any way as it concerns
> the governance of the non-legal aspects of Gentoo, except that they
> stand for election.  That is their mandate.
>
> But, others feel differently, and as I said if the council doesn't
> object to curtailing their authority, then I'll defer to them.
>
> Rich
>

I like what Tomáš proposed and I am in favor of the new CoC.

I also believe the council should not try to enforce the CoC. This is
something for devrel/userrel to do. The council should be the judge if
someone disagrees with
what devrel/userrel decided so he/she can appeal to another authority.
But for the day-to-day conflicts, I see no reason for the Council to
get involved. Imho this will
introduce another layer of bureaucracy without good reasons.

--
Regards,
Markos Chandras - Gentoo Linux Developer
http://dev.gentoo.org/~hwoarang

Re: [gentoo-project] Gentoo Code of Conduct

[Tomáš Chvátal]

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

2013/5/24 Markos Chandras <hwoarang@gentoo.org>

>
> I like what Tomáš proposed and I am in favor of the new CoC.
>
> I also believe the council should not try to enforce the CoC. This is
> something for devrel/userrel to do. The council should be the judge if
> someone disagrees with
> what devrel/userrel decided so he/she can appeal to another authority.
> But for the day-to-day conflicts, I see no reason for the Council to
> get involved. Imho this will
> introduce another layer of bureaucracy without good reasons.
>
> I think you just wrongly understood what Rich ment with the council.

It was more about situation where member is in both in council and devrel,
where he should not be at first decision and only be in appealing organ
(council).
But if other guys from council think it is no biggie we can drop the
sentence. I am really indiferent about it.

Tom

[-- Attachment #2: Type: text/html, Size: 1331 bytes --]

Re: [gentoo-project] Gentoo Code of Conduct

[Roy Bamford]

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

On 2013.05.24 12:46, Tomáš Chvátal wrote:
> Hello guys,
> 
> after last bunch of mails and internal complains I decided it is time
> to do
> something proactive.
> 
> So I give you revised Gentoo Code of Conduct.
> 
[snip]
> 
> Cheers
> 
> Tom
> 

Tom,

I would delete everything from "Examples of inappropriate behavior" to 
the credits at the end. Escalation, punishment and appeal is already 
covered by devrel documentation.

This will avoid the, "Well, its not listed so its ok" reaction.

If you want to say anything about enforcement in the CoC remind readers 
that everyone is responsible for enforcement.  Its key to defusing the 
situations covered by the CoC that a reminder is delivered very 
quickly.  That's in part why the Proctors project failed ... the 
elapsed time between an incident arising and a response. Even a few 
hours is too long. 

-- 
Regards,

Roy Bamford
(Neddyseagoon) a member of
elections
gentoo-ops
forum-mods
trustees

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

Re: [gentoo-project] Gentoo Code of Conduct

[Rich Freeman]

On Sun, May 26, 2013 at 7:32 AM, Roy Bamford <neddyseagoon@gentoo.org> wrote:
> I would delete everything from "Examples of inappropriate behavior" to
> the credits at the end. Escalation, punishment and appeal is already
> covered by devrel documentation.
>

I suspect that lack of punishment was basically the whole reason the
original CoC was written, and the whole reason the topic came up
again.

> If you want to say anything about enforcement in the CoC remind readers
> that everyone is responsible for enforcement.

That sounds a bit like nobody is responsible for enforcement.  The
only thing devs can do to basically do what they're already doing -
having running arguments on the lists.  The only way to block
inappropriate behavior is to moderate it.

Whether we want to do that is up to the community, but the existing
CoC is fine as-is if you don't want to do anything about enforcement,
IMHO.

Rich

Re: [gentoo-project] Gentoo Code of Conduct

[Roy Bamford]

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

On 2013.05.26 13:40, Rich Freeman wrote:
> On Sun, May 26, 2013 at 7:32 AM, Roy Bamford 
> <neddyseagoon@gentoo.org>
> wrote:
> > I would delete everything from "Examples of inappropriate behavior"
> to
> > the credits at the end. Escalation, punishment and appeal is 
> already
> > covered by devrel documentation.
> >
> 
> I suspect that lack of punishment was basically the whole reason the
> original CoC was written, and the whole reason the topic came up
> again.
> 
> > If you want to say anything about enforcement in the CoC remind
> readers
> > that everyone is responsible for enforcement.
> 
> That sounds a bit like nobody is responsible for enforcement.  The
> only thing devs can do to basically do what they're already doing -
> having running arguments on the lists.  The only way to block
> inappropriate behavior is to moderate it.
> 
> Whether we want to do that is up to the community, but the existing
> CoC is fine as-is if you don't want to do anything about enforcement,
> IMHO.
> 
> Rich
> 
> 

We have already tried the <small group> is responsible for enforcement 
approach.  

Even if we encourage everyone to intervene, most won't, for many 
reasons, so in practice we are back to the <small group> again.
 
-- 
Regards,

Roy Bamford
(Neddyseagoon) a member of
elections
gentoo-ops
forum-mods
trustees

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

Re: [gentoo-project] Gentoo Code of Conduct

[Ian Stakenvicius]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 26/05/13 08:40 AM, Rich Freeman wrote:
> On Sun, May 26, 2013 at 7:32 AM, Roy Bamford
> <neddyseagoon@gentoo.org> wrote:

> 
>> If you want to say anything about enforcement in the CoC remind
>> readers that everyone is responsible for enforcement.
> 
> That sounds a bit like nobody is responsible for enforcement.  The 
> only thing devs can do to basically do what they're already doing
> - having running arguments on the lists.  The only way to block 
> inappropriate behavior is to moderate it.

Alternatively, it empowers any dev to help stop this behaviour, rather
than just the moderators.  Sort of the same way bullying needs to be
dealt with -- if the whole community takes responsibility for treating
it as unacceptable, and calls on it right away, then things are a lot
more effective than relegating to a relatively small set of
authorities (although of course, there will always be a need for those
authorities too).


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlGiFOgACgkQ2ugaI38ACPDETAD/cG1BBrDSfsQHQrZjgnsUanw7
JfM5RAPRaA3C9wVPuEYA/jgHoGwGRkBVYvywNn7lnAZqw8vVDOR/ivy41QOkiUJC
=YCot
-----END PGP SIGNATURE-----

Re: [gentoo-project] Gentoo Code of Conduct

[Rich Freeman]

On Sun, May 26, 2013 at 9:58 AM, Ian Stakenvicius <axs@gentoo.org> wrote:
> Alternatively, it empowers any dev to help stop this behaviour, rather
> than just the moderators.  Sort of the same way bullying needs to be
> dealt with -- if the whole community takes responsibility for treating
> it as unacceptable, and calls on it right away, then things are a lot
> more effective than relegating to a relatively small set of
> authorities (although of course, there will always be a need for those
> authorities too).

By all means try it out, but I suspect that such a system will
generally just preserve the status quo.  Maybe that is fine, but I
doubt that counting on everybody to send 100 off-list emails to the
offender every time somebody gets out of line seems unlikely to work.

Rich

Re: [gentoo-project] Gentoo Code of Conduct

[Denis Dupeyron]

On Fri, May 24, 2013 at 5:46 AM, Tomáš Chvátal <scarabeus@gentoo.org> wrote:
> after last bunch of mails and internal complains I decided it is time to do
> something proactive.

I have to applaud the effort but I unfortunately have to warn you that
you are fighting windmills here. The core of the problem is that rules
are useless long-term if nobody enforces them. That takes somebody
with enough balls to make the bold moves. I am typically that person
at devrel but both because it's getting old and (to put it mildly) I'm
not very supported in that approach I mostly gave up. The other thing
is I used to do a lot of pro-active work trying to keep people in
check. I took so much heat that I mostly gave that up too. It also
takes an enormous amount of time.

Bottom line is, and I'm weighing my words very carefully after years
of seeing all this from the inside: nobody cares enough.

Denis.

Re: [gentoo-project] Gentoo Code of Conduct

[Andreas K. Huettel]

[-- Attachment #1: Type: Text/Plain, Size: 1224 bytes --]

Am Sonntag, 26. Mai 2013, 17:06:07 schrieb Denis Dupeyron:
> 
> Bottom line is, and I'm weighing my words very carefully after years
> of seeing all this from the inside: nobody cares enough.
> 

Well... Let's put it like this.

Sometime a while ago an oldtimer dev attacked a newbie dev on IRC, basically 
just because the newbie did his job properly, and this would have resulted in 
additional work for the oldtimer. 

I took the liberty of telling the old guy to stfu and not interfere.

Immediately, several others, who had not followed the issue at all, started 
directing comments at me, telling me I was wrong. To my immense amusement, 
they then gave emphasized statements how things should be done, and that was 
exactly how the *newbie* did it!

Now, I dont care that much anymore. However, I would suggest... If we do 
update our code of conduct we should make one thing very clear in the code of 
conduct or devrel guidelines or whatever: Independent of how many thousands of 
commits on g-x86 you did or do, 

Noone in gentoo is irreplaceable enough to justify gross misbehaviour.

-- 

Andreas K. Huettel
Gentoo Linux developer 
dilfridge@gentoo.org
http://www.akhuettel.de/


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 966 bytes --]

Re: [gentoo-project] Gentoo Code of Conduct

[Panagiotis Christopoulos]

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

On 19:06 Sun 26 May     , Andreas K. Huettel wrote:
> ... 
> Now, I dont care that much anymore. However, I would suggest... If we do 
> update our code of conduct we should make one thing very clear in the code of 
> conduct or devrel guidelines or whatever: Independent of how many thousands of 
> commits on g-x86 you did or do, 
> 
> Noone in gentoo is irreplaceable enough to justify gross misbehaviour.
> 

++ 

-- 
Panagiotis Christopoulos ( pchrist )
    ( Gentoo Lisp Project )

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

Re: [gentoo-project] Gentoo Code of Conduct

[Dale]

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

Andreas K. Huettel wrote:
> Well... Let's put it like this. Sometime a while ago an oldtimer dev attacked a newbie dev on IRC,
basically just because the newbie did his job properly, and this would
have resulted in additional work for the oldtimer. I took the liberty of
telling the old guy to stfu and not interfere. Immediately, several
others, who had not followed the issue at all, started directing
comments at me, telling me I was wrong. To my immense amusement, they
then gave emphasized statements how things should be done, and that was
exactly how the *newbie* did it! Now, I dont care that much anymore.
However, I would suggest... If we do update our code of conduct we
should make one thing very clear in the code of conduct or devrel
guidelines or whatever: Independent of how many thousands of commits on
g-x86 you did or do, Noone in gentoo is irreplaceable enough to justify
gross misbehaviour.

Since I moderate a website I'll add this.  When I volunteered to be a
moderator on the other site, I explained that for me to put my time and
effort in, the same rules apply to EVERYONE.  The same punishment
applies to EVERYONE who breaks the rules.  No preferential treatment for
anyone.  We talked for about 2 hours over the phone on this subject. 
After my explanation, and them seeing the logic to it, I was accepted as
a moderator.

Not to long ago, a important member violated a rule, rather large one at
that, and I took action.  At first, the owner was not happy then I
reminded him of the phone conversation.  Me moderating is a volunteer
position and I'm not paid for it.  If there is going to be double
standards, find someone else.  Double standards only lead to problems. 
Yes, the user was a VIP but the rules apply to the people who own the
site too.  They wouldn't post what that user did.  They know better. 
After the owner settled down a bit and I posted the rule I applied, then
he apologized for his reaction.  I have not been questioned for
enforcing a rule since.

My point is, I been using Gentoo for about 10 years, 2003.  I'm dalek on
the forums.  Yea, I was here when -dev was a sewer of a place and I
wouldn't subscribe much less post anything.  As it is now, -dev is a
MUCH better place to be even tho I rarely post anything.  If you are
going to set up rules and have them enforced, shall I recommend they
apply to everyone in the same way, regardless of what they do or how
long they have been here?  If you are not going to do that, spend your
time on fixing bugs and writing code and let this drop before you waste
time on it.  There won't be any point in going further.

No, I don't want to moderate -dev.  I don't read most things, just the
stuff that as a user I want to see coming around the corner, /usr and
init* and such as that.  I already help on two sites as it is.

Dale

:-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!


[-- Attachment #2: Type: text/html, Size: 3509 bytes --]

Re: [gentoo-project] Gentoo Code of Conduct

[Robin H. Johnson]

On Fri, May 24, 2013 at 01:46:38PM +0200, Tomáš Chvátal wrote:
> Basic social consents that our project works with are:
>  - Be considerate
>  - Be responsible
>  - Be respectful
>  - Be collaborative
>  - Support others in the community and get support from them

Beyond this, can we as a community suggest some useful resources on
encouraging good practices, rather than listing bad practices?

I'll start off with two things that have come to mind from this thread.

1.
Buddhist ethics principles, primarily the concept of 'Right speech' (but
much of the rest of the Buddhist principles are also useful):
https://en.wikipedia.org/wiki/Noble_Eightfold_Path#Right_speech

2.
Elsewhere in this thread it was noted that some long-standing developers
were being oppressive to new developers, but didn't realize it. To
counter that, I think that the original essay by Peggy McIntosh, 
"White Privilege: Unpacking the Invisible Knapsack" would be a useful
read:
http://www.amptoons.com/blog/files/mcintosh.html

-- 
Robin Hugh Johnson
Gentoo Linux: Developer, Trustee & Infrastructure Lead
E-Mail     : robbat2@gentoo.org
GnuPG FP   : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85