From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org,
openembedded-devel@lists.openembedded.org,
openembedded-members@lists.openembedded.org,
tsc@lists.openembedded.org
Subject: Invitation to attend the first TSC / Workgroup meeting
Date: Fri, 26 Jul 2013 17:32 +0100 [thread overview]
Message-ID: <2188465.MKAfj8q3MG@helios> (raw)
Hi all,
As you may be aware, the role of the OpenEmbedded TSC (Technical Steering
Committee) is currently evolving. Over the past few meetings we have
discussed the need to focus our efforts on settings technical direction and
resolving conflicts (should they arise), instead of spearheading specific
technical contributions. While each of us expects to continue to be involved
in technical contributions, we want to reach out to the OpenEmbedded community
and work to establish a better way for work to be done.
Time: Tuesday July 30th - 16:00 GMT (9am PDT, 11am CDT, 12 EDT, 18:00 CEST,
17:00 BST)
Where: Freenode IRC, channel #oe
The goal of this meeting is to introduce the work that we have been doing, the
type of tasks that we believe need to be done, and a discussion with the
community on establishing one or more task-force/working group/etc in order to
accomplish the tasks.
While we are still working on a more formal agenda, we expect to cover topics
such as:
* janitor bugs (general cleanup/maintenance activities)
* eglibc -> glibc transition happening in the broader community
* oe-core/meta-oe work
* python 3 transition
Cheers,
Paul
[Thanks to Mark Hatle for the above text]
--
Paul Eggleton
Intel Open Source Technology Centre
reply other threads:[~2013-07-26 16:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2188465.MKAfj8q3MG@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-members@lists.openembedded.org \
--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