From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org,
openembedded-devel@lists.openembedded.org
Subject: Public TSC / OE Workgroup meeting today
Date: Tue, 14 Jan 2014 10:08:35 +0000 [thread overview]
Message-ID: <7166127.YkfX3aIoNI@helios> (raw)
Hi all,
There will be a public OpenEmbedded TSC/workgroup meeting today - there
wouldn't normally be one scheduled but there was quite a lot of discussion
last time (which is a good thing!). If you're interested in discussing long-
term technical efforts around the OpenEmbedded project please join us on
irc.freenode.net in channel #oe at
17:00 GMT (9am PST, 11am CST, 12 EST, 18:00 CET) today.
Topics we covered last meeting:
* Qt 4 / 5 recipes in OE-Core
* Rising bug count in Bugzilla and what we can do about it
* (briefly) Patch review/merging process
* Absentee layer maintainers
Issues we didn't get to last time (that weren't resolved on the mailing list):
- janitorial day/week?
- "bitbake world" failures scrub
- initrdscripts/init-live needs work
- lava evaluation
- website and other infrastructure issues
- next release
New issues for discussion are also welcome.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next reply other threads:[~2014-01-14 10:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 10:08 Paul Eggleton [this message]
2014-01-14 12:13 ` [oe] Public TSC / OE Workgroup meeting today Martin Jansa
2014-01-14 12:13 ` Martin Jansa
2014-01-14 12:55 ` [oe] " Phil Blundell
2014-01-14 13:33 ` Martin Jansa
2014-01-14 13:33 ` [OE-core] " Martin Jansa
2014-01-14 15:54 ` [oe] " Mark Hatle
2014-01-14 16:10 ` Trevor Woerner
2014-01-14 16:45 ` Trevor Woerner
-- strict thread matches above, loose matches on Subject: below --
2014-04-01 10:45 Paul Eggleton
2014-03-04 14:04 Paul Eggleton
2014-01-07 15:12 Paul Eggleton
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=7166127.YkfX3aIoNI@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--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.