public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposing fundamental changes to DevRel
Date: Mon, 21 Jun 2010 18:44:30 +0300	[thread overview]
Message-ID: <4C1F88DE.1080708@gentoo.org> (raw)
In-Reply-To: <4C1A85C5.4070305@gentoo.org>

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

On 06/17/2010 11:29 PM, Sebastian Pipping wrote:
> Petteri,
> 
> 
> On 06/17/10 17:45, Petteri Räty wrote:
>> We communicate in English but that doesn't mean we all the same cultural
>> background. My native language doesn't do small talk and doesn't have a
>> word for please. Of course when writing English I try use please when
>> required by the other party but sugar coating wouldn't have changed what
>> I wanted to communicate with my message.
> 
> the point of this thread is not the introduction of "sugar coating"
> (pretending to be nice in my words) as you call it.  To me it's about
> turning Gentoo into a friendly and helpful community. (So it's actually
> not just about tone but the things coming before the tone, too.)
> 

On 06/17/10 09:52, Petteri Räty wrote:
> >> Wrong mailing list. This thread belongs to gentoo-project.
>
> that's what I am referring to with "tone in Gentoo".
> I want the other 80% of you on the council.
>

How would you have liked this to be written then?

> 
>> It would just increase the time
>> needed to write the message and raise the risk of getting misunderstood.
>> A short and to the point message is the easiest to understand.
> 
> Yes, being friendly may take more words.  Isn't it in your own best
> interest to have the other side not get pissed?  Isn't that worth a few
> more words?
> 

I don't see anything unfriendly in my first reply. This thread doesn't
have anything technical and as just doesn't belong to gentoo-dev. As
DevRel lead I think it's my duty to remind developers how our mailing
lists are meant to be used.

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

  reply	other threads:[~2010-06-21 15:42 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17  0:00 [gentoo-dev] Proposing fundamental changes to DevRel Sebastian Pipping
2010-06-17  0:33 ` Jorge Manuel B. S. Vicetto
2010-06-17  1:05   ` Ben de Groot
2010-06-17 14:37   ` Sebastian Pipping
2010-06-17 22:46     ` Sebastian Pipping
2010-06-17 23:36       ` Alec Warner
2010-06-17 23:36   ` Richard Freeman
2010-06-17  0:41 ` Mike Frysinger
2010-06-17  7:56   ` [gentoo-dev] " Duncan
2010-06-17 15:10     ` Sebastian Pipping
2010-06-17 15:52       ` Petteri Räty
2010-06-18  2:38         ` Duncan
2010-06-17  0:41 ` [gentoo-dev] " Jeremy Olexa
2010-06-17  7:52 ` Petteri Räty
2010-06-17 15:00   ` Sebastian Pipping
2010-06-17 15:45     ` Petteri Räty
2010-06-17 16:20       ` Ben de Groot
2010-06-17 16:33         ` Petteri Räty
2010-06-17 16:21       ` Patrick Lauer
2010-06-17 20:09         ` Sebastian Pipping
2010-06-17 20:39           ` Patrick Lauer
2010-06-17 20:29       ` Sebastian Pipping
2010-06-21 15:44         ` Petteri Räty [this message]
2010-06-17 11:16 ` Markos Chandras
2010-06-17 18:28 ` Roy Bamford
2010-06-17 18:47 ` Roy Bamford
2010-06-18  4:06   ` Jeroen Roovers

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=4C1F88DE.1080708@gentoo.org \
    --to=betelgeuse@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