View difference between Paste ID: xZZ6h2Q3 and jeeGWbYu

 OpenEmbedded Technical Steering Committee
 18 June 2013
 
 Attendees:
   Koen (koen)
   Fray (fray)
   Paul (bluelightning)
   Khem (khem)
   Richard (RP)
 Apologies:
 
 Notes: Jefro
 
 Agenda at a glance:
 
 1. pick a chair
 2. new issues
 3. lingering issues
 	a. role of the TSC
-	a. oe-classic recipe migration status
+	b. elections
-	b. oe-core release
+
-	c. meta-oe appends/overlayed recipes RFC
+	a. oe-core release
-	d. 1.5 planning
+	b. meta-oe appends/overlayed recipes RFC
-	e. python 3
+	c. python 3
-	f. release status notification
+	d. release status notification
 5. infrastructure
 	a. 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
 
 ___________________________________
 2. new issues
 
-a. elections
+
 
 ___________________________________
 3. lingering issues
 
 a. role of the TSC
 	(http://lists.linuxtogo.org/pipermail/openembedded-core/2013-April/038756.html)
 	proposal: monthly IRC meeting to replace one of the bi-weekly TSC meetings, open to all
 	split the TSC role in two.. have a infrastructure, etc TSC similar to now.. as well as 'resolve technical conflicts'
 => 	post RFC on mailing list (RP)
 	defer vote
 
 b. elections
 =>	jefro to flag the board, recommend defer elections (DONE)
 ___________________________________
 4. projects in progress - status
 
 a. oe-core release
 	release status emails very well received
 	stabilisation period for 1.5 M1 now
 	teething issues w/ gcc 4.8
 	trending OK
 
 b. meta-oe appends/overlayed recipes RFC
 	still remaining: busybox and gst-ffmpeg bbappends, xserver-nodm-init
 	Warning: PRINC is deprecated, the use of the PR server is recommended, see ...
 =>	issue warning, plan to make it an error in 1.5, revisit before release (RP)
 =>	document PRINC - PR server migration steps (fray)
 =>	proposal: error and a disable flag, revise RFC patch (fray)
 	RFC switching wholeheartedly to libav (bluelightning) sent, a few responses
 
 c. python 3
 	need to start informing people of it -now-
 	loop around to decide python version etc - no current update
 
 d. release status notification
 =>	maintain a wiki page to summarize release goals (jefro)
 
 ___________________________________
 5. infrastructure
 
 a. oe.org flooded
 => investigate YP hosting, kernel.org mirror (jefro)
 	monitor for now
 
 ___________________________________
 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
-=> fray will send to list after 1.4
+
 => going to mailing lists & someone should write a proposal
 => fray will send to list after 1.4
 
 
 ________________________________________________________________
 Raw Transcript