public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Council manifesto of sping
Date: Fri, 02 Jul 2010 17:50:29 +0200	[thread overview]
Message-ID: <4C2E0AC5.5000302@gentoo.org> (raw)
In-Reply-To: <AANLkTilM2jrglpI3MpHajmPv-mU2RPptVPhREX3SaF9b@mail.gmail.com>

Arun,


On 07/02/10 16:23, Arun Raghavan wrote:
> The problem is not noise. The problem is that an issue that needs to
> be escalated to Devrel could not be resolved by the involved
> developers or the people who were present at the time. Moreover, there
> are strong emotions from the devs (and often their friends too), and
> people will end up saying things that they may eventually regret.
> 
> Dragging this out in public /will/ polarise the community, result in
> more public conflict, very likely without a complete picture of the
> story on both sides being available. Devrel's purpose is to avoid
> this, and I believe this does work (we can debate their efficacy or
> how things can improve, but saying it doesn't work is unfair, IMO). I
> don't see how your proposal would deal with this fallout.

I think we're mixing up a few things by now:
- What cases should be handled in public, which shouldn't
- Does DevRel work effectively or not
- The special case of banning people

All I want to say right here is that:
- Not everything needs to be handle loudly and public
  (if I made that impression)
- I do believe in need for fundamental changes on DevRel
  (as introduced in a another thread earlier)

For the rest I propose to take this offline.

Best,



Sebastian



  reply	other threads:[~2010-07-02 15:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-19 19:56 [gentoo-dev] Gentoo Council 2010/2011 - Voting Roy Bamford
2010-06-19 21:06 ` [gentoo-dev] Manifesto for council election Tony "Chainsaw" Vroon
2010-06-20 11:19 ` [gentoo-dev] My Council manifest Petteri Räty
2010-06-20 13:47 ` [gentoo-dev] Re: Gentoo Council 2010/2011 - Voting Roy Bamford
2010-06-21 16:33 ` [gentoo-dev] Council manifesto of sping Sebastian Pipping
2010-06-21 18:20   ` Petteri Räty
2010-06-21 21:07     ` Sebastian Pipping
2010-06-21 19:25   ` Arun Raghavan
2010-06-21 21:36     ` Sebastian Pipping
2010-06-22  1:46       ` Brian Harring
2010-06-22  2:37         ` Sebastian Pipping
2010-06-22  5:13       ` Arun Raghavan
2010-06-22 10:02         ` [gentoo-dev] " Duncan
2010-06-22 10:24           ` Arun Raghavan
2010-06-30  0:45         ` [gentoo-dev] " Sebastian Pipping
2010-07-02 14:23           ` Arun Raghavan
2010-07-02 15:50             ` Sebastian Pipping [this message]
2010-07-02 17:30               ` Nirbheek Chauhan
2010-06-22  5:15       ` Arun Raghavan
2010-06-22  2:37   ` Alec Warner
2010-06-21 19:10 ` [gentoo-dev] My council manifesto Mark Loeser
2010-06-21 19:15   ` Arun Raghavan
2010-06-21 19:27     ` Mark Loeser
2010-06-21 19:30       ` Arun Raghavan
2010-06-21 21:19 ` [gentoo-dev] Gentoo Council 2010/2011 - Voting Mike Frysinger
2010-07-02 22:32 ` [gentoo-dev] Re: Gentoo Council 2010/2011 - Voting - Reminder Roy Bamford

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=4C2E0AC5.5000302@gentoo.org \
    --to=sping@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