From: Philip Balister <philip@balister.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: proposal to move cogl, clutter and related recipes from oe-core to dedicated meta-clutter layer
Date: Tue, 14 May 2013 12:23:34 -0400 [thread overview]
Message-ID: <51926506.5070302@balister.org> (raw)
In-Reply-To: <1368308951.11129.108.camel@ted>
On 05/11/2013 05:49 PM, Richard Purdie wrote:
>
> I will however raise the point that a lot of people currently have a
> tendency to "hide behind" me in discussions. They see me reply and
> assume that since I've said something, that is it and they can keep
> quiet. I want to be clear this isn't going to work as on this and some
> other topics, it looks like I'm a lone voice. If people do believe in a
> particular issue, they do need to stand up and add weight to an argument
> themselves.
I'd like to emphasize this point. Sometimes, Richard seems to be all
alone defending decisions that are made. If he is supporting your
position, support him publicly. Otherwise, there is a perception in the
community that Richard is acting alone.
Also, getting a variety of viewpoints out really helps technical
discussion. Sometimes it is the little details in individual use cases
that become really important.
Philip
next prev parent reply other threads:[~2013-05-14 16:41 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 15:11 proposal to move cogl, clutter and related recipes from oe-core to dedicated meta-clutter layer Tomas Frydrych
2013-05-08 15:23 ` Phil Blundell
2013-05-08 16:34 ` Tomas Frydrych
2013-05-08 15:23 ` Richard Purdie
2013-05-08 16:20 ` Tomas Frydrych
2013-05-10 9:05 ` Richard Purdie
2013-05-10 10:56 ` Tomas Frydrych
2013-05-10 11:32 ` Richard Purdie
2013-05-10 16:39 ` Tomas Frydrych
2013-05-10 17:19 ` Richard Purdie
2013-05-10 20:22 ` Otavio Salvador
2013-05-10 20:37 ` Mark Hatle
2013-05-10 21:15 ` Otavio Salvador
2013-05-13 9:30 ` Tomas Frydrych
2013-05-13 15:41 ` Phil Blundell
2013-05-13 15:44 ` Burton, Ross
2013-05-14 9:14 ` Tomas Frydrych
2013-05-14 16:55 ` Paul Eggleton
2013-05-15 9:19 ` Tomas Frydrych
2013-05-15 9:49 ` Paul Eggleton
2013-05-15 11:35 ` Tomas Frydrych
2013-05-15 11:53 ` Otavio Salvador
2013-05-15 13:20 ` Andreas Oberritter
2013-05-15 14:09 ` Paul Eggleton
2013-05-15 16:34 ` Tomas Frydrych
2013-05-15 16:54 ` Otavio Salvador
2013-05-15 17:22 ` Paul Eggleton
2013-05-15 17:30 ` Richard Purdie
2013-05-15 17:36 ` Otavio Salvador
2013-05-15 18:24 ` Paul Eggleton
2013-05-15 19:28 ` Otavio Salvador
2013-05-15 20:49 ` Phil Blundell
2013-05-16 9:01 ` Tomas Frydrych
2013-05-16 10:35 ` Phil Blundell
2013-05-16 11:21 ` Tomas Frydrych
2013-05-16 14:35 ` Phil Blundell
2013-05-17 12:30 ` Paul Eggleton
2013-05-16 9:22 ` Tomas Frydrych
2013-05-15 19:43 ` Richard Purdie
2013-05-16 9:21 ` Tomas Frydrych
2013-05-10 21:07 ` Martin Jansa
2013-05-10 22:18 ` Richard Purdie
2013-05-11 20:39 ` Otavio Salvador
2013-05-11 21:49 ` Richard Purdie
2013-05-14 16:23 ` Philip Balister [this message]
2013-05-13 9:31 ` Tomas Frydrych
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=51926506.5070302@balister.org \
--to=philip@balister.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=richard.purdie@linuxfoundation.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