Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Phil Blundell <pb@pbcl.net>, openembedded-members@lists.openembedded.org
Cc: tsc@lists.openembedded.org, openembedded-core@lists.openembedded.org
Subject: Re: OE, the TSC and the future
Date: Fri, 26 Jul 2013 15:54:19 +0100	[thread overview]
Message-ID: <2088951.PevEKBo15A@helios> (raw)
In-Reply-To: <1374793592.2861.60.camel@pb-ThinkPad-R50e>

On Friday 26 July 2013 00:06:32 Phil Blundell wrote:
> On Mon, 2013-07-08 at 13:51 -0500, Sean Hudson wrote:
> > it seems to me that the need for a group to
> > arbitrate on technical matters is valuable enough, by itself, to keep
> > the TSC.
> > This applies even if that function is utilized infrequently.
> 
> I remain slightly dubious about that, not least because the TSC's recent
> track record in terms of having its decisions implemented hasn't been
> entirely stellar.

As far as recent history goes, my recollection is we've only had one decision 
(on shell function indentation) that was backed out by maintainers. I think I 
speak not just for myself when I say those on the TSC that were opposed didn't 
feel it was big enough of an issue to try to battle for the original decision 
to be upheld. That doesn't mean that we aren't prepared to resolve technical 
disputes in future, as per the original TSC mandate, nor does it mean that 
there won't be a need for that in future.

> It's also been quite noticeable that, except for Richard (who started
> this thread), none of the current members of the TSC have offered any
> opinion on what the future role of that body ought to be or what value
> it brings.

I guess I hadn't responded yet because I felt like this thread was for others 
outside the TSC to express their thoughts first.
 
> > In considering the future of the TSC, I offer the opinion that in the
> > future,
> > tactical concerns shouldn't be the primary business for the TSC. Rather,
> > I'd like to see the TSC become more strategically focused. In particular,
> > I'd like
> > to have the TSC produce a vision for OE in the 2-3 year time frame
> 
> ... this is a good suggestion; I'm sure we'd benefit from a bit more of
> a strategic vision and perhaps this is indeed the direction that the TSC
> ought to evolve in.

FWIW, I agree. I don't think we should necessarily lose sight of the TSC as a 
body for resolving technical disputes however.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


      parent reply	other threads:[~2013-07-26 14:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18 16:23 OE, the TSC and the future Richard Purdie
2013-06-27 14:48 ` Philip Balister
2013-06-27 15:38   ` Richard Purdie
2013-06-27 16:08     ` Mark Hatle
2013-07-05 23:46 ` Phil Blundell
2013-07-08 18:51   ` Sean Hudson
     [not found]     ` <1374793592.2861.60.camel@pb-ThinkPad-R50e>
2013-07-26 14:54       ` Paul Eggleton [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=2088951.PevEKBo15A@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-members@lists.openembedded.org \
    --cc=pb@pbcl.net \
    --cc=tsc@lists.openembedded.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