public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Bruce A. Locke" <blocke@shivan.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Why I left the Gentoo Linux development team
Date: 16 Apr 2002 03:42:59 -0400	[thread overview]
Message-ID: <1018942980.27360.21.camel@kodiak.chronospace.org> (raw)
In-Reply-To: <1018861624.19528.6.camel@willow.uwyn.office>

On Mon, 2002-04-15 at 05:07, Geert Bevin wrote:
> Hi everyone,
> 
> since a number of people privately asked me why I decided to leave the
> Gentoo Linux development team, I wrote an article that explains what
> drove me to this decision. For those that are interested, it can be read
> here : http://www.uwyn.com/resources/gentoo_departure.html

You know, I really shouldn't say this in public, but any sympathy I had
for you just vanished when I read that doc.  You post a log of
conversation between two people showing at best an interest in a C++
based portage2 but no guarantee thats the path portage would be going
down.  And then you down play the objections people had to your plan of
portage 2.  I was one of the people against the idea and I wasn't the
only one by far.  

You know, things change, plans change, people change.  If you feel your
work had been thrown away unfairly thats one thing and a valid reason to
quit.  If you feel it was a waste of your time due to a lack of
communication or other people in the project not agreeing with your
work, thats life, thats opensource, deal.  If you don't agree with the
decisions then leave, if it were important enough I would.  But instead
of stating that and questioning the decision, you slander people in your
"excuse".

>From my experiences with you and based on the doc you posted I think you
should take a look at yourself before accusing anyone else of "tendency
to monopolise".  I was there in the channel when you two had a
discussion, and drobbins, the Chief Architect and Project Lead, vetoed
one of your ideas.  You couldn't handle not being in complete control of
portage v1 so you resigned from being the portage v1 release engineer
and then commenced into bitching to me and other people.

In that document you present your view point and manage to slander a
couple other developers in the process.  Although I don't really see why
you wrote the doc and decided to announce it far and wide unless your
intent was to tarnish existing developers and the Gentoo project over
all.  As a (minor) developer that angers me.

I think people should see there is more then one view point and I'm
frankly infuriated that you brought up a private matter between a
developer (Vitaly) and a few other certain members of the development
team _that had nothing to do with the reason you cleam to have left
Gentoo_.

I'm going to end it there... 

As a developer you made many good contributions to Gentoo and we will
miss you as a developer.  Its too bad it had to end in a public temper
tantrum.  I hope you have success in whatever you do.

-- 

Bruce A. Locke
blocke@shivan.org




      reply	other threads:[~2002-04-16  7:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-15  9:07 [gentoo-dev] Why I left the Gentoo Linux development team Geert Bevin
2002-04-16  7:42 ` Bruce A. Locke [this message]

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=1018942980.27360.21.camel@kodiak.chronospace.org \
    --to=blocke@shivan.org \
    --cc=gentoo-dev@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