From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: Openembedded Discussion
<openembedded-devel@lists.openembedded.org>,
openembedded-core@lists.openembedded.org
Subject: Re: Invitation: OpenEmbedded public TSC/workgroup meeting
Date: Tue, 10 Sep 2013 14:16:50 +0100 [thread overview]
Message-ID: <1893978.VDA3SxeMzl@helios> (raw)
In-Reply-To: <CANyK_8egdmC3tsFq2fZKbaqmxnpuruWyJPhbBgYEdMz-qqffKA@mail.gmail.com>
Hi Paul,
On Tuesday 10 September 2013 12:13:12 Paul Barker wrote:
> On 5 September 2013 19:52, Paul Eggleton <paul.eggleton@linux.intel.com>
> wrote:
> > Please join the OpenEmbedded TSC (Technical Steering Committee) this
> > coming Tuesday for a public IRC meeting to discuss ongoing community
> > technical work.
> >
> > As you may be aware, the role of the OpenEmbedded TSC is currently
> > evolving to focus our efforts on setting 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. The plan is to hold these public meetings on a monthly basis and
> > reduce separate TSC meetings to quarterly or as-needed.
> >
> > Time: Tuesday September 10th at 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 continue to discuss outstanding tasks,
> > discuss and collect any new tasks or issues, and establish 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:
> >
> > * SPDX integration, other licensing issues
> > * janitor tasks (general cleanup/maintenance activities)
>
> I'm unsure if I'll have internet access around this time as I'm
> travelling today. Incase I can't make it, I briefly want to say that
> we should set up a wiki page for non-urgent janitor tasks and try to
> make a list of those tasks which we think could easily be handled by a
> new contributor to OE/Yocto. That would hopefully make it easier for
> people to learn the ropes and get involved.
Absolutely. Between OE and the Yocto Project we do have a couple of wiki
pages:
http://www.openembedded.org/wiki/OpenEmbeddedJanitors
https://wiki.yoctoproject.org/wiki/Janitors
We need to work on getting this information into one place though and turning
it into a reasonable list with pointers on how people can get started.
> I assume that an IRC log will be posted after the meeting, is that correct?
That's correct.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-09-10 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 18:52 Invitation: OpenEmbedded public TSC/workgroup meeting Paul Eggleton
2013-09-10 11:13 ` Paul Barker
2013-09-10 13:16 ` Paul Eggleton [this message]
2013-09-10 20:32 ` [oe] " Frans Meulenbroeks
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=1893978.VDA3SxeMzl@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul@paulbarker.me.uk \
/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