Re: [OE-core] OE TSC Minutes 7 May 2013
On Tue, May 21, 2013 at 9:36 PM, Jeff Osier-Mixon je...@jefro.net wrote: OpenEmbedded Technical Steering Committee 7 May 2013 Attendees: Koen (koen) Khem (khem) Fray (fray) Paul (bluelightning) Richard (RP) Apologies: Notes: Jefro Agenda at a glance: 1. pick a chair 2. new issues 3. lingering issues a. systemd merge unhappiness 4. projects in progress - status a. oe-classic recipe migration status b. oe-core release c. systemd into master d. meta-oe appends/overlayed recipes RFC e. 1.5 planning 5. infrastructure a. mailing list moving to YP server, in progress b. oe.org flooded 6. projects deferred a. raise awareness of janitor list, QA bugs b. document whitespace changes to the shell c. raise ntp with the Yocto Project [RP] There are three issues I would like to comment on: 1. systemd migration: From what I see the only major step left over is to bury meta-systemd. The only appends found there are those for oe-core. I asked for this long time ago [1] and support was offered but... 2. indention: Reading between the lines there is some unhappiness on meta-oe using four spaces for shell and python code. I personally agree with Martin here because I have not seen a technical reason for shell requiring tabs so far. To me this looks like a style decision which increases the burden to submit for low-skilled people like me. Could somebody please enlighten me: For what technical reason do we need tabs in shell code? 3. xserver-nodm-init oe-core vs. meta-oe This is a long lasting issue and Martin commented on why there is a different approach in meta-oe [2]. One blocker for progress is xinput calibrator rework. Short story: I have a solution working here which is capable of starting calibrator by udev/systemd and can be invoked by an unprivileged user at any time. Unfortunately this solution has still too many issues to be submitted and from what I see now I won't find the time to fix them in the next future. So if anybody wants to unify xserver-nodm-init - feel free. Users can add xserver.common to images manually (and xinput calibrator is not really working anyway). If I could I would add an additional item on the agenda: gtk3-migration: In meta-gnome we are working with terribly old gnome recipes. These needed much backporting efforts to survive glib-2.36 / gcc 4.8 updates - and I don't think this increases code quality in any way - so it is more or less a useless effort which we will continue. * Are there plans for a step-by step migration? A good starter would be to solve libnotify 2/3 API issue. Is anybody else working on this / thinking about? * Are there plans to update gtk3 to 3.8.x to have wayland support? Cheers Andreas [1] http://lists.openembedded.org/pipermail/openembedded-core/2013-January/073596.html [2] http://lists.openembedded.org/pipermail/openembedded-core/2013-February/075336.html ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] OE TSC Minutes 7 May 2013
OpenEmbedded Technical Steering Committee 7 May 2013 Attendees: Koen (koen) Khem (khem) Fray (fray) Paul (bluelightning) Richard (RP) Apologies: Notes: Jefro Agenda at a glance: 1. pick a chair 2. new issues 3. lingering issues a. systemd merge unhappiness 4. projects in progress - status a. oe-classic recipe migration status b. oe-core release c. systemd into master d. meta-oe appends/overlayed recipes RFC e. 1.5 planning 5. infrastructure a. mailing list moving to YP server, in progress b. oe.org flooded 6. projects deferred a. raise awareness of janitor list, QA bugs b. document whitespace changes to the shell c. raise ntp with the Yocto Project [RP] Agenda Results 1. pick a chair koen ___ 2. new issues a. phil's questions about the role of the TSC (http://lists.linuxtogo.org/pipermail/openembedded-core/2013-April/038756.html) original charter is to look at issues, and attempt to resolve them the pull model removed a lot of the reason the TSC was created two functions of the TSC: working group/task force type activities and actual decision making also administrative functions 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 ___ 3. lingering issues a. systemd merge unhappiness ~ release status notification = maintain a wiki page to summarize release goals (jefro) = status emails (RP) - ongoing ___ 4. projects in progress - status a. oe-classic recipe migration status some recipes migrated but then kept in own layers also cherry picking parts of layers like meta-oe need some documentation on right way to synchronize b. oe-core release 1.4.1 is being worked on along with 1.3.2 c. dropped d. meta-oe appends/overlayed recipes RFC no avr32 support in public layers paul has patches to remove bbappends, pending discussion on ml everything uncontested has been sent for review qt4/qt tools stuff troublesome - still remaining: busybox and gst-ffmpeg bbappends, xserver-nodm-init = RFC switching wholeheartedly to libav (bluelightning) e. 1.5 planning RP on sabbatical 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-.. ___ 5. infrastructure a. mailing list moving to YP server in progress b. oe.org flooded refs to oe.org git should point to github = fix the oe wiki and reminder to ml (khem) = remove = investigate YP hosting, kernel.org mirror (jefro) ___ 6. projects deferred a. raise awareness of janitor list, QA bugs defer to after 1.4 b. document whitespace changes to the shell http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines http://www.openembedded.org/wiki/Styleguide https://wiki.yoctoproject.org/wiki/Recipe_%26_Patch_Style_Guide = still need to de-dup these, need a volunteer ask for volunteers after 1.4 (jefro) c. raise ntp with the Yocto Project [RP] immediate need addressed, reasonable default needed use LICENSE_FLAGS - non-commercial no default set after Paul's changes RP raised with YP AB = going to mailing lists someone should write a proposal = fray will send to list after 1.4 Raw Transcript (8:59:19 AM) Jefro: good heavens, everyone is here (8:59:29 AM) koen: yes (8:59:33 AM) koen: 17:55 koen this must be a record, every tsc member present 5 minutes early :) (8:59:47 AM) ***RP is here :) (9:00:22 AM) Jefro: there isn't some disaster I haven't heard of yet, is there? (9:01:05 AM) Jefro: I even have an agenda: http://pastebin.com/0nSZm90B (9:01:48 AM) koen: shall I chair? (9:02:15 AM) RP: koen: fine with me (9:02:24 AM) RP: Are fray, khem, bluelightning alive? (9:02:35 AM) bluelightning: hi all, yes I'm here (9:02:58 AM) RP: I'd like to add python3 to the agenda somewhere (9:03:11 AM) koen: 4f ? (9:03:55 AM) koen: no objections, so 4f python3 (9:04:03 AM) Jefro: (added to my copy) (9:04:10 AM) koen: let's wait a bit for khem and fray to wake up (9:04:38 AM) fray: sorry.. I'm here (9:05:46 AM) ***fray is busy playing with the new office build server.. :) (9:05:48 AM) fray: was distracted (9:06:22 AM) koen: looks like we have quorum, let's hope khem shows up soon (9:06:45 AM) koen: 1 - pick a chair - done (9:06:47 AM) fray: sounds good (9:06:48 AM) koen: 2 - New issues (9:07:09 AM) ***RP isn't aware of any (9:07:17 AM) koen: me neither (9:07:22 AM) bluelightning: nor me (9:07:26 AM) RP: Actually, I guess there is Phil's email (9:07:37 AM) koen: which one specifically? (9:07:38 AM) RP: His questions about the role of the TSC (9:07:40 AM) bluelightning: oh
Re: [OE-core] OE TSC Minutes 7 May 2013
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.ja...@gmail.com signature.asc Description: Digital signature ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
