View difference between Paste ID: Cz0faSCS and 22BCQPQm
SHOW: | | - or go back to the newest paste.
1
OpenEmbedded Technical Steering Committee
2-
23 October 2012
2+
20 November 2012
3
4-
Attendees: Koen, Paul, Khem, Richard
4+
Attendees: Koen, Paul, Khem, Richard, Mark
5-
Apologies: Mark
5+
6
________________________________________________________________
7
Agenda & Results
8
9
1. pick a chair
10
11
___________________________________
12
2. new issues
13
14
 a. RFC for the secondary toolchain (fray)
15
    how to document as best practice?
16
        possibly sample secondary toolchain layer as template
17
        no changes to oe-core, possibly add an include file
18
-> in progress
19
20
 b. RPM and package feeds
21
        packages_rpm, rootfs_rpm doesn't use Zypper
22
        fray proposes replacing with SMART after 1.3 release
23
        smaller footprint, python based
24
        -> fray will write proposal after 1.3
25
-> in progress
26
27
 c. patchwork queue
28
    bluelightning did a massive clearout of patchwork, got rid of 3 pages
29
    a number of oe-classic patches left
30
    koen notes that git hooks catch only 80% of patches, and then only for master
31
    known to fail with accented names
32
=> koen to go through what is left in patchwork for meta-oe
33
=> bluelightning to send note to ml re oe-classic patches
34
35
 d. raise ntp with the Yocto Project [RP]
36
 
37
 e. secondary toolchain document
38
	http://www.openembedded.org/wiki/Adding_a_secondary_toolchain
39
	
40
 f. wiki
41
 
42
 g. oe-classic recipe migration status
43
 
44
 h. FILESDIR & FILESPATH
45
___________________________________
46
3. lingering issues
47
48
 a. raise awareness of "janitor" list, QA "bugs"
49
50
 b. pre/post install scripting (fray)
51
     holding for 1.4
52
53
 c. document whitespace changes to the shell
54
    RP edited OE style guide with new info, linked to YP
55
        => fray to update patch guidelines
56
57
 d. documentation
58
    need someone to work on OE wiki pages
59
        RP, bluelightning, fray to hopefully work on it together @ELCE
60
61
___________________________________
62
4. status
63
64
 a. oe-core release
65
	good to go with the branch as it stands now
66
	1.4 is open for development now
67
68
 b. infrastructure
69
    Tom & Martin working on setting up jenkins
70
71
 c. 1.4 planning
72
   PR issues
73
   pre/post install scripting
74
   SMART
75
   systemd into master