[openbeos] Re: Team Leaders
- From: "Hugo Santos" <linn@xxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Mon, 18 Feb 2002 23:32:30 WET
No need to push on Michael.. i'm sure he's doing the best he can.. as
most obos developers are.
i don't really get why did people get so annoyed..
Hugo santos
> I think Michael is doing a super-human job. No need to punish him
> for what
> seemed to be a collective decision by all team leaders. Personally,
> I think
> the release was "a good thing", on several levels.
> Take care.
>
> > -----Original Message-----
> > From: romt [SMTP:romt@xxxxxxxxxxxxxx]
> > Sent: Tuesday, February 19, 2002 9:54 AM
> > To: openbeos@xxxxxxxxxxxxx
> > Subject: [openbeos] Re: Team Leaders
> >
> > Just a small suggestion,
> >
> > maybe Michael should step down as "head" of the OBOS project and
> > slip
> > back
> > as head of the kernel dev . Then using all the team leaders,
> > michael
> > included, form a committee of sorts that they can discuss between
> > each
> > other
> > of when stuff should be released. Obviously this is sought of
> > happening,
> > but
> > I think that this project has become too big for one person to be
> > in
> > charge
> > of.
> >
> > Now this is not to criticise all the hard work that michael has put
> > in,
> > more
> > that it's alot easier to blame one person for something, than it is
> > a
> > group
> > who've made a united decision.
> >
> > I suggest this more in the hope of eleviating some of the
> > "hostility" that
> > seems to have sprung up over the weekend :-). Keep up the good
> > work, "one"
> > and all
> >
> > Matt
> > ----- Original Message -----
> > From: "Michael Phipps" <mphipps1@xxxxxxxxxxxxxxxx>
> > To: <openbeos@xxxxxxxxxxxxx>
> > Sent: Monday, February 18, 2002 12:29 PM
> > Subject: [openbeos] Re: Team Leaders
> >
> >
> > > >Sorry if I over-reacted a bit in the way that I sent my critics
> > > > to the
> > public mailing list, but it isn't so much different from hearing
> > > >about a obos release the first time on public websites. Why
> > > > didn't you
> > tell us on this mailing list that you wanted to do a release?
> > >
> > > A number of reasons.
> > > First off, this is *NOT* a developer mailing list, as you assert
> > > below.
> > There are > 450 people on here. I promise you, if we had 450
> > > developers, we would be done with R2 by now. :-)
> > > Secondly, this was/is a first release. *NOTHING* went according
> > > to plan.
> > Just as I planned. :-)
> > > I know that there are a number of people on this list who are
> > > members of
> > the BeOS media. And if I said "Hey - there will be a release
> > > on 2/14", then nothing happened, we would have *0* credability
> > > left.
> > Now,
> > I know that this release is a disappointment to many.
> > > But it is a release, of sorts. The next one will be better in
> > > every way.
> > > Be aware that there are various reasons for the quality. All of
> > > those
> > issues have been noted and will be corrected for next time.
> > > It is not our job to point fingers. And honestly, there is only
> > > one
> > person
> > who knows the whole story about the release. He is also the
> > > guy who takes the responsibility. Me. Don't even ask whose fault
> > > it is.
> > Blame me. Because, truth be told, that is what it means to be a
> > > leader. You get all the praise (which you then double in quantity
> > > and
> > heap
> > on the people who made it happen) and all of the blame
> > > (which you swallow with sufficient quantities of Milk of
> > > Magnesia). So
> > any
> > quality issues are all my fault. Things released that shouldn't
> > > have been? All me. Don't like the packaging? All me. But, you
> > > know what?
> > I
> > would still have done it, even had I known. We did something
> > > that most open source projects never do. We shipped something.
> > > And we
> > have
> > a goal (see below) and a plan, of sorts, to get there.
> > > None of our releases would be perfect. If anyone on this list was
> > > ever
> > part of a Be beta program, feel free to tell us how perfect
> > > their beta releases were. :-)
> > >
> > > Our *GOAL*, and I have a nervous, queasy feeling even saying
> > > this, is to
> > have another release in about a month.
> > > And every month, around the middle of the month, do another
> > > release. Up
> > until R1 ships. Then, we will see. THAT IS NOT A PROMISE!
> > > It is a goal. An ideal situation.
> > >
> > > >Even
> > > >some developers of these apps didn't know there apps where
> > > > released.
> > Hey,
> > we are subscribed to a *developer* mailing list, so
> > > >why aren't we
> > > >informed here instead of reading about it on public websites?
> > >
> > > Honestly, because after all the hours of work at my real job,
> > > plus about
> > 8
> > hours of building the release, I went to bed. :-/
> > >
> > > >read on...
> > > >First, being a team leader was a matter of "first come, first
> > > > have it".
> > They weren't choosen to be team leaders because
> > > >they have themselves qualified in a competition. Now please
> > > > noone get
> > me
> > wrong, I'm sure all team leaders are doing great
> > > >work, because
> > > >they all decided to take that position out of passion the this
> > > > project.
> > I
> > really don't want to blame anyone. And I don't grasp for
> > > >their
> > > >position. All I wanted to do is express my thoughts (and
> > > > emotions) on
> > what happened.
> > >
> > > I am very curious as to your basis for this. See - I picked the
> > > team
> > leaders. And I know what my thought process was.
> > > And I have never explained it to anyone, publically. It really
> > > has
> > nothing
> > to do with first come, first served. Although there
> > > were cases where a person came along AFTER I had chosen a team
> > > lead who
> > I
> > thought might have made a good team lead, too.
> > > But I did not just throw the first person into the hole.
> > >
> > > I looked for people (at least, according to their emails) who had
> > leadership experience, who were knowledgable, who seemed
> > > mature enough (no 313373 c0derz), etc. Looking at the list, and
> > > the
> > results, I don't think that the choices were all that bad.
> > >
> > >
> > >
> > >
> >
> >
> >
> ----------------------
> CONFIDENTIALITY NOTICE
> ----------------------
> This email is intended only to be read or used by the addressee.
> The information contained in this e-mail message may be confidential
> information. If you are not the intended recipient, any use,
> interference
> with, distribution, disclosure or copying of this material is
> unauthorised
> and prohibited. Confidentiality attached to this communication is not
> waived
> or lost by reason of the mistaken delivery to you.
>
> If you have received this message in error, please delete it and
> notify us
> by return e-mail or telephone Aristocrat Technologies Australia Pty
> Limited
> on +61 2 9413 6300.
Other related posts:
