From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: TSC Meetings for the meeting of June
Date: Thu, 01 Jul 2010 10:56:11 +0200 [thread overview]
Message-ID: <i0hl7b$8uu$1@dough.gmane.org> (raw)
In-Reply-To: <4C2B446A.5040301@freyther.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 30-06-10 15:19, Holger Freyther wrote:
> In regard to the TSC, what mode of operation do you propose? We freeze
> the tree until all items are implemented in the order they are proposed?
> We find people driving a topic?
In this specific case you (or the TSC) choose to work on a extremely
intrusive and controversial *cosmetic* change first instead of tackling
the some of the (IMO more important) items agreed on earlier:
* making QA checks be enabled by default
* promoting new style staging and converting existing recipes
* promoting bbclassextend and converting existing recipes
* fixing nativesdk
By skipping over those, without saying why and going for the cosmetic
change the TSC is sending out a signal that they do NOT care about
quality, only appearance. In the past I was proud about how OE handled
things by the things you yourself created, like insane.bbclass, the
first edition of tinderbox, etc. But recently only 2 groups of OE
developers seem to care about quality, the SHR and angstrom folk. Those
are the only 2 distros that have the QA checks enabled. Due to the
nature of OE other benefit from the awesome work Martin and Khem have
been doing, but it feels a bit one sided to me.
Since nearly all OE developers can't work fulltime on OE, I would
propose that the TSC sends out a few "call to action" mails, describing
the tasks that need doing and some guidance on how they want to see it
done. I will *gladly* help out, but I need to know what needs doing and
avoid duplicate work.
It would help to have a "completed action items", "in progress action
items" and "action items that noone is working on" list in the TSC
minutes (or wiki) to keep track of stuff.
And of course a big thank you to all the people working on QA that I
didn't mention.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMLFgrMkyGM64RGpERAtCVAJ4xp7Lxx91AwSUN7DgEwxasSjr4gACgi2/n
qbbTDqsfC2RlFjxhRglNtZ4=
=zIjM
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-07-01 9:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 13:03 TSC Meetings for the meeting of June Holger Freyther
2010-06-09 13:25 ` Michael Smith
2010-06-09 13:53 ` Frans Meulenbroeks
2010-06-09 14:57 ` Chris Larson
2010-06-09 16:53 ` Philip Balister
2010-06-09 17:37 ` Khem Raj
2010-06-11 8:06 ` Frans Meulenbroeks
2010-06-11 18:29 ` Koen Kooi
2010-06-11 21:37 ` Richard Purdie
2010-06-12 7:37 ` Koen Kooi
2010-06-12 11:12 ` Frans Meulenbroeks
2010-06-12 11:47 ` Graeme Gregory
2010-06-12 12:20 ` Frans Meulenbroeks
2010-06-30 10:26 ` Holger Freyther
2010-06-30 11:05 ` Koen Kooi
2010-06-30 13:04 ` Frans Meulenbroeks
2010-06-30 13:19 ` Holger Freyther
2010-07-01 8:56 ` Koen Kooi [this message]
2010-07-01 11:52 ` Frans Meulenbroeks
2010-07-01 12:07 ` Graeme Gregory
2010-07-01 13:43 ` Frans Meulenbroeks
2010-07-01 17:59 ` Mark Brown
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='i0hl7b$8uu$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.