public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Denis Dupeyron <calchan@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Who is willing to be lead?
Date: Sat, 10 Apr 2010 13:27:36 -0600	[thread overview]
Message-ID: <x2x7c612fc61004101227xc5bb6506i468a9d8d39250329@mail.gmail.com> (raw)
In-Reply-To: <k2ke117dbb91004100738t517eb6e1pe6dfa73ddb12891c@mail.gmail.com>

Ben,

Petteri was proposing an idea. He is being creative and is trying to
help. The only way of knowing if his idea is good is to discuss it and
later try it if people are interested.

You, on the other hand, have lately been increasingly critical (which
is good) but not constructively. You obviously have a lot of energy
but at no point have you offered your contribution. You haven't
offered to help the teams you've been criticizing and you haven't
proposed any real idea (website redesign, recruiters). Also you're
criticizing without knowing what is happening when the information is
publicly available (you're asking for a discussion on the metadata
idea and it was a topic last month, the devrel issue is being tackled
and it started before your rant).

On Sat, Apr 10, 2010 at 8:38 AM, Ben de Groot <yngwin@gentoo.org> wrote:
> I am willing to follow real leaders

Willing to follow? Wow, that's ballsy. Now I understand why you needed
to tell the world about it.

> who inspire and lead by example,

There are lots of good role models to follow in Gentoo. All those who
work their ass off trying to make this distribution better, and use
the mailing lists as a tool to share ideas but not for immature
political rantings.

> You've just shown a striking lack of such leadership.
>
> No cheers this time,

And you've shown a striking lack of respect for somebody who's been so
dedicated to Gentoo for more time than you've been a developer, and
without whom you wouldn't even be a developer as he was your
recruiter. This is so wrong.

Credibility is among these things which take a long and hard work to
build up and can completely blow up at any time. Don't waste yours.

Denis.



  parent reply	other threads:[~2010-04-10 19:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-10 13:53 [gentoo-dev] Who is willing to be lead? Petteri Räty
2010-04-10 14:00 ` Markos Chandras
2010-04-10 14:11   ` Petteri Räty
2010-04-12 10:23   ` Roy Bamford
2010-04-10 14:38 ` Ben de Groot
2010-04-10 14:44   ` Petteri Räty
2010-04-10 19:27   ` Denis Dupeyron [this message]
2010-04-10 20:17     ` Ben de Groot
2010-04-10 20:56       ` Petteri Räty
2010-04-10 21:18         ` Ben de Groot
2010-04-10 21:23           ` Petteri Räty
2010-04-10 21:37             ` Ben de Groot
2010-04-10 21:43               ` Petteri Räty
2010-04-10 22:06                 ` Denis Dupeyron
2010-04-10 22:10                   ` Petteri Räty
2010-04-10 22:54                     ` Denis Dupeyron
2010-04-10 23:44                       ` Ben de Groot
2010-04-11  2:30                         ` Richard Freeman
2010-04-11  1:21                       ` Sebastian Pipping
2010-04-10 22:15                   ` Ben de Groot
2010-04-10 21:06   ` Steve Rosiak
2010-04-10 21:19 ` Petteri Räty
  -- strict thread matches above, loose matches on Subject: below --
2010-04-10 14:09 Vincent-Xavier JUMEL
2010-04-11  0:20 ` 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=x2x7c612fc61004101227xc5bb6506i468a9d8d39250329@mail.gmail.com \
    --to=calchan@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