public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: Retirement
Date: Mon, 11 Aug 2008 00:31:26 +0000 (UTC)	[thread overview]
Message-ID: <pan.2008.08.11.00.31.25@cox.net> (raw)
In-Reply-To: 7c612fc60808101640l31e7f248ybf9eeba60c5faeeb@mail.gmail.com

"Denis Dupeyron" <calchan@gentoo.org> posted
7c612fc60808101640l31e7f248ybf9eeba60c5faeeb@mail.gmail.com, excerpted
below, on  Mon, 11 Aug 2008 01:40:58 +0200:

> On Mon, Aug 11, 2008 at 1:18 AM, Nikos Chantziaras <realnc@arcor.de>
> wrote:
>> They always say that stuff but never bother explaining what the
>> direction they wish for actually is.  As a user I get the impression
>> that there's some kind of evil Cabal.
> 
> Most of the Gentoo developer population is made of young males with a
> natural tendency to overreaction and suboptimal communication skills
> (and I'm not implying it's the case of the original poster). So, if I
> were you, I wouldn't bother too much to read in between the lines of
> these retirement messages.

That, and by the time it comes to retirement, one has generally been thru 
the arguments several times already, the people that need to know why in 
general already do, and there's a feeling it's not worth rehearsing old 
positions and bringing up old arguments the one last time.  The time for 
that has already passed by the time someone's announcing their 
retirement, the decision has been made, it's all water under the bridge 
now (as the saying goes) and it's time to move on, with a clean break, no 
longer blaming anyone or etc as that's what one does /before/ it gets to 
this point.

So, indeed, I'm a KDE user here, and it's time to wish them well...

Thanks guys for all the hard work, the product of which I'm running 
(still KDE 3.5.9, here) as I type this.  Be well, and hope to see you 
around the community!  There's plenty of projects out there that can use 
your help! =8^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman




  reply	other threads:[~2008-08-11  0:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-10 22:26 [gentoo-dev] Retirement Bo Ørsted Andresen
2008-08-10 22:35 ` Donnie Berkholz
2008-08-10 23:18   ` [gentoo-dev] Retirement Nikos Chantziaras
2008-08-10 23:40     ` Denis Dupeyron
2008-08-11  0:31       ` Duncan [this message]
2008-08-11  4:51     ` Alec Warner
2008-08-11  5:46       ` Nikos Chantziaras
2008-08-11  7:45       ` Ciaran McCreesh
2008-08-11 13:19         ` Patrick Lauer
2008-08-11 13:31           ` Anthony Metcalf
2008-08-12  0:26             ` Duncan
2008-08-12 16:02               ` Jeroen Roovers
2008-08-11 13:34           ` George Prowse
2008-08-11 10:27       ` David Leverton
2008-08-11  7:25 ` Steve Long
2008-08-11  9:35 ` [gentoo-dev] Retirement Santiago M. Mola
2008-08-11 10:58 ` Jorge Manuel B. S. Vicetto
  -- strict thread matches above, loose matches on Subject: below --
2006-11-03 19:49 Seemant Kulleen
2006-11-03 20:37 ` [gentoo-dev] Retirement Christian Faulhammer
2006-11-03 19:15 [gentoo-dev] Retirement Jon Portnoy
2006-11-04  1:20 ` [gentoo-dev] Retirement Duncan

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=pan.2008.08.11.00.31.25@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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