From: Finn Thain <fthain@telegraphics.com.au>
To: gentoo-osx@lists.gentoo.org
Subject: Re: [gentoo-osx] Arch Testing Policy and Procedures
Date: Wed, 7 Sep 2005 14:39:38 +1000 (EST) [thread overview]
Message-ID: <Pine.LNX.4.63.0509071409570.22106@loopy.telegraphics.com.au> (raw)
In-Reply-To: <431DEA52.40105@gentoo.org>
On Tue, 6 Sep 2005, Grobian wrote:
> I have the impression that a few major things *have* to be done. This
> requires 'action' and taking discisions that probably not everyone is
> going to be happy with.
Yes. You also made this point earlier in the thread, but it got snipped
(I'll repeat it here:)
> > > If Mike Frysinger would jump in today or tomorrow, here in this
> > > team, we'd have to listen to "OSX sucks" all day long, but also "if
> > > we do it like this, then it works, even on osx".
And that is one of the main reasons why, in big business, an executive or
team of executives from outside the organisation (often from overseas)
might be installed by a board to do a particular job (e.g. a
reorganisation).
This is not always because the vision or ability is lacking in-house, it
is because no-one in-house wants the job (makes to many enemies to say
"gentoo-macos sucks"), or because noone in-house will be given sufficient
respect ("he is just one of us, and we don't see a problem") or because
noone in-house can be trusted to do it (doesn't really apply here, since
nepotism and corruption aren't the issue).
-f
--
gentoo-osx@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-07 4:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-04 2:29 [gentoo-osx] Arch Testing Policy and Procedures Lina Pezzella
2005-09-04 10:57 ` Grobian
2005-09-04 19:22 ` Lina Pezzella
2005-09-04 20:53 ` Grobian
2005-09-05 3:42 ` Kito
2005-09-05 6:28 ` Grobian
2005-09-06 17:35 ` Nathan
2005-09-06 19:13 ` Grobian
2005-09-07 4:39 ` Finn Thain [this message]
2005-09-07 7:27 ` Grobian
2005-09-07 4:57 ` Finn Thain
2005-09-07 7:21 ` Grobian
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=Pine.LNX.4.63.0509071409570.22106@loopy.telegraphics.com.au \
--to=fthain@telegraphics.com.au \
--cc=gentoo-osx@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