public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Richard Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Tone in Gentoo
Date: Sun, 20 Jun 2010 20:00:51 -0400	[thread overview]
Message-ID: <4C1EABB3.8050904@gentoo.org> (raw)
In-Reply-To: <4C1D1618.8030708@gentoo.org>

On 06/19/2010 03:10 PM, Jorge Manuel B. S. Vicetto wrote:
> I can assure you that if someone goes to #gentoo-forums and tries to
> tell the forums team what tone should be used in that channel, we'll
> kindly ask the person to stop or to leave. This is one of the "public"
> and exposed channels and thus we have a tone with that in mind, but
> we're not going to set our tone according to the demands of a developer
> that is not even part of the team.

I was not suggesting that tone in Gentoo was up to the discretion of any 
individual developer - neither myself, nor you, nor the head of 
infra/forums/etc.  The tone in Gentoo is up to Gentoo.  Fortunately we 
have a forum for deciding what Gentoo wants - we elect them annually.

> What would grant
> any non-member of a team the right to demand how the members of the team
> should act amongst themselves in their private room?

Simple - the room belongs to Gentoo as a whole.  You're certainly free 
not to listen to me, but I and others are free to point out that this 
isn't good for Gentoo.  I certainly wouldn't take it upon myself to 
enforce the CofC, but I certainly would urge those responsible for 
governing the distro to do so.

> About the "legal right", that isn't true. There are a few misconceptions
> in your statement. Even though the Foundation is the body which holds
> the Gentoo brand, trademarks and logo, it's not the Foundation that sets
> the rules for joining and be part of the Gentoo Developers Community.
> Furthermore, being a Gentoo developer doesn't mean you can join any team
> you want or that you have a "right" to go to any #gentoo-* channel. In
> case you have any doubt, I can give you a list of quite a few channels
> most developers don't have access to.

Your statement is partially correct - obviously if I am a stockholder in 
Google I can't choose to just waltz onto the corporate campus and go 
around as I please, merely by virtue of being a shareholder.

However, a shareholder of Google certainly is able to speak out about 
actions within the company that they feel damage it, and their elected 
representatives (the board) can give power to anybody (including 
themselves) to waltz around and put things in order.  This starts with 
their authority to hire and fire the CEO at whim.

Ultimately, if anything contains the name "Gentoo" and represents itself 
as being associated with a linux distribution, then it is using a 
trademark owned by the Gentoo Foundation.  In the end, any use of Gentoo 
trademarks is completely at the discretion of the Foundation.

> If you insist, to address the question that access lists for #gentoo-*
> channels can be set by Freenode (our main IRC network), you should know
> that the only people Freenode will listen to regarding that are the
> members of the Freenode Gentoo Group Contacts. The people in that group
> were not chosen by the Foundation nor do they respond to it.

Well, this is getting a bit silly, but they'd certainly answer to a 
cease and desist, or those hosting their servers certainly would.  It 
would obviously never come to that.  Go ahead and try to register 
#microsoft-press-releases and see if being named the official contact 
gets you anywhere.

> Also, please never forget that being part of Gentoo is a "privilege" and
> not a "right".

On that we certainly agree.  It really wasn't my intention to suggest 
that somehow anybody was personally beholden to me.  I really am just 
stating my opinion, as are you.

> As an example, even though I use my gentoo cloak online, you don't have
> any right to impose a behaviour into me in my private channel.

Sure, I cannot, personally.  However, Gentoo certainly can.  At the very 
least I'd expect devs to generally conduct themselves in a manner where 
such things aren't necessary to even bring up.

> We have a loosely-knit community that is able to provide a reasonable
> product "Gentoo Linux". Let's try to avoid killing it by wanting to
> impose a certain "mentality" or "behaviour" into others and let's try to
> respect each other and learn to live in a community.

Well, the whole principle of the CofC is that it imposes behaviors on 
those who wish to use Gentoo media, or be Gentoo staff.

That said, I really don't suggest that anybody need be heavy-handed. 
Nor do I suggest that my personal opinion should be the one that rules 
Gentoo (I would say the same regarding your opinion as well).  In the 
end that's all we're doing - you say that infra decides what happens on 
#gentoo-infra, and I say that they don't (well, not ultimately - 
certainly I'd suggest that the trustees/council should of course 
delegate channel moderation to the team that uses the channel, and only 
intervene if necessary).

What I would say is that I encourage those who are in the trustees and 
council to recognize the importance of this issue, and I ask that they 
consider that tone really does matter.  We elect these bodies to speak 
for Gentoo, and I think that this is an issue where Gentoo could stand 
to be heard.  Gentoo has spoken before in issuing the Code of Conduct - 
perhaps now we just need to actually enforce it.

Rich



  reply	other threads:[~2010-06-21  0:01 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16  3:33 [gentoo-dev] Tone in Gentoo Sebastian Pipping
2010-06-16  3:51 ` Mike Frysinger
2010-06-16  5:03 ` Alec Warner
2010-06-17  0:14   ` Jorge Manuel B. S. Vicetto
2010-06-17  0:32     ` Sebastian Pipping
2010-06-17  9:51       ` Ciaran McCreesh
2010-06-17  9:58         ` Auke Booij
2010-06-17 10:08           ` Ciaran McCreesh
2010-06-17 10:17             ` Angelo Arrifano
2010-06-17 10:01         ` Dale
2010-06-17 10:08         ` Angelo Arrifano
2010-06-17 10:15           ` Angelo Arrifano
2010-06-17 10:17           ` Ciaran McCreesh
2010-06-17 10:26             ` Angelo Arrifano
2010-06-17 12:51             ` Sebastian Pipping
2010-06-17  2:08     ` Jacob Godserv
2010-06-16  5:43 ` Jeroen Roovers
2010-06-16 15:36   ` [gentoo-dev] " Nikos Chantziaras
2010-06-16 18:18     ` Alec Warner
2010-06-16 18:47       ` Nikos Chantziaras
2010-06-16 22:55         ` Sebastian Pipping
2010-06-16 19:31     ` Jeroen Roovers
2010-06-17  0:02       ` Sebastian Pipping
2010-06-16 19:40     ` Roy Bamford
2010-06-16 22:33       ` Sebastian Pipping
2010-06-17  5:47         ` Duncan
2010-06-17 19:29         ` Roy Bamford
2010-06-18  3:43           ` Jeroen Roovers
2010-06-19  2:51             ` Sebastian Pipping
2010-06-16 22:14   ` [gentoo-dev] " Sebastian Pipping
2010-06-17  3:24     ` Jeroen Roovers
2010-06-17 12:20       ` Sebastian Pipping
2010-06-17 17:33         ` Jeroen Roovers
2010-06-16 16:39 ` "Paweł Hajdan, Jr."
2010-06-16 17:07   ` Angelo Arrifano
2010-06-16 22:44     ` Sebastian Pipping
2010-06-16 22:47   ` Sebastian Pipping
2010-06-16 22:58     ` Steve Dibb
2010-06-17  6:59     ` "Paweł Hajdan, Jr."
2010-06-17  0:01   ` Jorge Manuel B. S. Vicetto
2010-06-17  0:17     ` Sebastian Pipping
2010-06-17  0:43       ` Jorge Manuel B. S. Vicetto
2010-06-17  1:13     ` Ben de Groot
2010-06-17  6:46       ` "Paweł Hajdan, Jr."
2010-06-17  4:21   ` [gentoo-dev] " Duncan
2010-06-19  2:25 ` [gentoo-dev] " Sebastian Pipping
2010-06-19  3:20   ` Jorge Manuel B. S. Vicetto
2010-06-19  4:35     ` Angelo Arrifano
2010-06-19  9:00     ` [gentoo-dev] " Duncan
2010-06-19  9:37       ` Brian Harring
2010-06-19 16:33         ` Sebastian Pipping
2010-06-19 14:37     ` [gentoo-dev] " Sebastian Pipping
2010-06-19 14:58       ` Denis Dupeyron
2010-06-19 15:34         ` Nirbheek Chauhan
2010-06-19 16:02           ` Sebastian Pipping
2010-06-19 17:07             ` Nirbheek Chauhan
2010-06-19 17:50       ` Wulf C. Krueger
2010-06-19 18:23         ` Sebastian Pipping
2010-06-19 20:38         ` Ben de Groot
2010-06-19  4:45   ` Jeremy Olexa
2010-06-19 16:15     ` Sebastian Pipping
2010-06-19 17:06       ` Jorge Manuel B. S. Vicetto
2010-06-19 17:40         ` Richard Freeman
2010-06-19 19:10           ` Jorge Manuel B. S. Vicetto
2010-06-21  0:00             ` Richard Freeman [this message]
2010-06-21  4:39               ` Arun Raghavan
2010-06-19  6:43   ` Patrick Lauer
2010-06-19  7:10     ` "Paweł Hajdan, Jr."
2010-06-19  9:32       ` Matti Bickel
2010-06-19 10:54       ` Ben de Groot
2010-06-19 17:44         ` Richard Freeman
2010-06-19 17:59         ` Ciaran McCreesh
2010-06-19 18:57           ` Sebastian Pipping
2010-06-19 19:16             ` Ciaran McCreesh
2010-06-19 19:37               ` Sebastian Pipping
2010-06-19 21:03           ` Ben de Groot
2010-06-19 21:20             ` Ciaran McCreesh
2010-06-19 21:48               ` Patrick Lauer
2010-06-19 21:57             ` David Leverton
2010-06-19 22:01               ` Patrick Lauer
2010-06-19 22:13                 ` David Leverton
2010-06-19 22:05               ` Domen Kožar
2010-06-19 22:18                 ` David Leverton
2010-06-19 18:17         ` Dale
2010-06-19 16:20     ` Sebastian Pipping
2010-06-19 21:27       ` Patrick Lauer

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=4C1EABB3.8050904@gentoo.org \
    --to=rich0@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