public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: Retirement
Date: Mon, 11 Aug 2008 08:46:04 +0300	[thread overview]
Message-ID: <g7ojn1$p73$1@ger.gmane.org> (raw)
In-Reply-To: <b41005390808102151h372e0d17l7ce9677a17f15b57@mail.gmail.com>

Alec Warner wrote:
> On Sun, Aug 10, 2008 at 4:18 PM, Nikos Chantziaras <realnc@arcor.de> wrote:
>> Donnie Berkholz wrote:
>>> On 00:26 Mon 11 Aug     , Bo Ørsted Andresen wrote:
>>>> My retirement is probably long overdue as I haven't really been active
>>>> for several months. It is now clear to me that Gentoo is not moving in the
>>>> direction I had wished for and the last council election indicates that most
>>>> current Gentoo developers appear to be satisfied with this current
>>>> direction. Therefore farewell. If anybody wants to reach me I can be reached
>>>> at bo.andresen at zlin.dk.
>>> Adios guys, and thanks for all the work you've put into Gentoo while you
>>> were here! Best of luck on your future endeavors.
>> 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.
> 
> Despite our best efforts Gentoo is not a fun-loving community where
> everyone gets along.
> If you want to call the fact that the majority of developers want to
> go in direction 'X' a cabal; then so be it.
> 
> Many folks are happy at the current pace of development.  I imagine
> these two folks were frustrated at the lack
> of new features in the ebuild spec that were readily available in
> kdebuild-1 and decided to move on.  More power to them I say.

I must apologize for using the word "Cabal".  I don't know the 
developers who resigned at all, nor do I have any clue about the reasons 
they departed.  Leaving with a "Gentoo is not going in the direction I 
want" is equivalent to "Gentoo is going in the wrong direction" and 
makes the resignation sound political.  I don't get why anyone would 
resign because of the ebuild spec, but anyway.  Resignations in general 
don't tend to be too honest.  "I'm bored dudes, farewell" would probably 
be perfectly fine.




  reply	other threads:[~2008-08-11 12:09 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
2008-08-11  4:51     ` Alec Warner
2008-08-11  5:46       ` Nikos Chantziaras [this message]
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='g7ojn1$p73$1@ger.gmane.org' \
    --to=realnc@arcor.de \
    --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