All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: openembedded-core git repository
Date: Mon, 24 Jan 2011 21:57:28 +0000	[thread overview]
Message-ID: <1295906248.14388.46605.camel@rex> (raw)
In-Reply-To: <ihkrpo$uft$1@dough.gmane.org>

On Mon, 2011-01-24 at 22:43 +0100, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 24-01-11 17:39, Philip Balister wrote:
> > On 01/19/2011 06:48 AM, Graeme Gregory wrote:
> >> Hi, this email is sent as an ordinary member of OE.
> >>
> >> It seems to be on a technical level we are agreed that we should split
> >> parts of OE out into the so called openembedded-core which will have a
> >> stricter commit access and higher QA requirements on changes.
> >>
> >> I therefore think it is time to actually create the repository and let
> >> the people who are interested in merging the good stuff from poky with
> >> the good stuff from openembedded to create our "core". I don't think
> >> there is any need to wait on the political part of the Yocto/OE
> >> collaboration as its something we have agreed in principal to do anyway.
> >>
> >> I would request then that the TSC drive this forward with the server
> >> admins and create this repo so work can happen.
> > 
> > 
> > Has anything happened on this email? Has the TSC had a meeting to
> > discuss? I know it has only been a week, but people are starting to do
> > work based on these ideas and need some support from the TSC.
> 
> At this point I'm going to call for a vote of non confidence in the TSC.
> If they can't be bothered to speak up in an important matter like this,
> we'd be better of without them.

I've kept a low profile on this issue since I'm obviously heavily
involved with Yocto and hence it could be argued I'm not impartial. I
had hoped someone else on the TSC would therefore pick up this
discussion but that hasn't happened. I have driven issues in the past,
this is one I really can't drive alone.

The TSC have been having trouble managing to organise meetings,
organising minutes and have not been very responsive recently. There are
a whole spectrum of reasons for that but at a time when OE really needs
technical guidance this is a problem.

The message here isn't to the oe-members list in the correct form so
this isn't an official vote at this time but if it were, I think I'd
find myself in the unusual position of voting in favour of a vote of no
confidence for a group I'm actually part of :/.

I'd actually like to see people with the technical understanding and
time to spend help guiding OE such Koen and Khem on the TSC.

Cheers,

Richard




      reply	other threads:[~2011-01-24 21:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19 14:48 openembedded-core git repository Graeme Gregory
2011-01-19 15:32 ` Eric Bénard
2011-01-19 16:01   ` Graeme Gregory
2011-01-19 15:33 ` Frans Meulenbroeks
2011-01-19 15:59   ` Graeme Gregory
2011-01-19 17:14     ` Khem Raj
2011-01-19 18:52     ` Frans Meulenbroeks
2011-01-19 22:43       ` Graham Gower
2011-01-20 10:21         ` Frans Meulenbroeks
2011-01-20 15:24           ` Chris Larson
2011-01-19 19:43 ` Philip Balister
2011-01-21 11:22   ` Bernhard Guillon
2011-01-24 16:39 ` Philip Balister
2011-01-24 17:48   ` Khem Raj
2011-01-25 11:05     ` Koen Kooi
2011-01-25 14:49       ` Frans Meulenbroeks
2011-01-25 17:53         ` Tom Rini
2011-01-25 18:19           ` Chris Larson
2011-01-25 21:26             ` Richard Purdie
2011-01-25 15:23       ` Richard Purdie
2011-01-25 15:56         ` Koen Kooi
2011-01-25 18:28         ` Khem Raj
2011-01-25 18:24       ` Khem Raj
2011-01-24 21:43   ` Koen Kooi
2011-01-24 21:57     ` Richard Purdie [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=1295906248.14388.46605.camel@rex \
    --to=rpurdie@rpsys.net \
    --cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.