From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core <openembedded-core@lists.openembedded.org>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: OE TSC Minutes 7 May 2013
Date: Tue, 21 May 2013 23:45:39 +0200 [thread overview]
Message-ID: <20130521214539.GF32431@jama> (raw)
In-Reply-To: <CA+YB3rYf0Tt181v+zAqCwjKk74uP88Zoaht_+FMuS7ee2tJRfQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2171 bytes --]
On Tue, May 21, 2013 at 12:36:54PM -0700, Jeff Osier-Mixon wrote:
> TSC could chair it but make it a public IRC thing
> -> proposal: monthly IRC meeting to replace one of the bi-weekly TSC
> meetings, open to all
> timezone will be an issue
> => think about for next meeting
I really like this idea, I think it will improve situation with:
status updates - people can watch it immediately on IRC, instead
of waiting for minutes
lack of community input - easier for people to comment on issues or add
to agenda when they see discussion about related topic
community involvement - seeing some AR discussed a month ago is too late
to volunteer
> f. python 3
> hard to support both py2 and 3
> two issues: python3 on target, using p3 for bitbake
> don't think we can reasonably support both
> make the switch in the 1.5 timeframe?
> need to start informing people of it -now-..
p3-only looks good to me, I would be happy to help testing this and then
drop p2 from my minimalistic chroot. There are also some external tools
like opkg-utils (IIRC this one is 99% p3 compatible now, I can take care
of remaining).
> (9:32:11 AM) RP: For 3a, I'd agreed to provide status updates. I've
> now provided two of these
> (9:32:24 AM) Jefro: wiki page is not yet done
> (9:32:27 AM) RP: I'm trying to turn it into a habit
> (9:32:50 AM) RP: Did people like/dislike them?
I like them.
> (9:36:03 AM) bluelightning: it's worth noting I'm aware that some
> people have migrated recipes and then kept them in their own layers
> (9:36:35 AM) bluelightning: which is not hugely bad but it would be
> nice if they could send them somewhere more appropriate
> (9:36:59 AM) RP: bluelightning: any idea why they're doing that?
> Simply don't know any different?
For many recipes I've used meta-shr as "staging" area to test it on more
builders and probably by more people before moving them to meta-oe.
But it's also easy to forget them in "staging" area, when they just
work for me (as I have meta-shr always included) and nobody shows any
interest in them.
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-05-21 21:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 19:36 OE TSC Minutes 7 May 2013 Jeff Osier-Mixon
2013-05-21 21:45 ` Martin Jansa [this message]
2013-05-22 8:31 ` Andreas Müller
2013-05-22 10:31 ` [oe] " Burton, Ross
2013-05-22 11:01 ` Andreas Müller
2013-05-22 13:41 ` Burton, Ross
[not found] ` <519CCFFF.2060506@windriver.com>
2013-05-22 14:49 ` Martin Jansa
2013-05-22 15:11 ` Paul Eggleton
2013-05-22 15:19 ` Martin Jansa
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=20130521214539.GF32431@jama \
--to=martin.jansa@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox