Advertisement
Guest User

Untitled

a guest
Jul 2nd, 2013
81
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.42 KB | None | 0 0
  1. OpenEmbedded Technical Steering Committee
  2. 18 June 2013
  3.  
  4. Attendees:
  5. Koen (koen)
  6. Fray (fray)
  7. Paul (bluelightning)
  8. Khem (khem)
  9. Richard (RP)
  10. Apologies:
  11.  
  12. Notes: Jefro
  13.  
  14. Agenda at a glance:
  15.  
  16. 1. pick a chair
  17. 2. new issues
  18. 3. lingering issues
  19. a. role of the TSC
  20. b. eglibc
  21. 4. projects in progress - status
  22. a. oe-core release
  23. b. meta-oe appends/overlayed recipes RFC
  24. c. python 3
  25. d. release status notification
  26. 5. infrastructure
  27. a. oe.org flooded
  28. 6. projects deferred
  29. a. raise awareness of "janitor" list, QA "bugs"
  30. b. document whitespace changes to the shell
  31. c. raise ntp with the Yocto Project [RP]
  32.  
  33. ________________________________________________________________
  34. Agenda & Results
  35.  
  36. 1. pick a chair
  37. bluelightning
  38.  
  39. ___________________________________
  40. 2. new issues
  41.  
  42. ___________________________________
  43. 3. lingering issues
  44.  
  45. a. role of the TSC
  46. review discussion on mailing list
  47. elections deferred
  48.  
  49. b. eglibc
  50. http://www.eglibc.org/archives/patches/msg01268.html
  51. maintainers (Mentor) removing differences btw eglibc, upstream glibc
  52. would like to deprecate & remove option groups
  53. then unable to configure items out
  54. potentially ruining poky-tiny and others
  55. -> poll users to see if actually being used
  56. alternatively, find someone willing to maintain
  57. khem proposes replacing option groups with pure kconfig
  58. => raise eglibc issues on mailing list (fray)
  59. => get kconfig stuff discussed and proposed to glibc (khem)
  60.  
  61. ___________________________________
  62. 4. projects in progress - status
  63.  
  64. a. oe-core release
  65. current phase: M2
  66.  
  67. b. meta-oe appends/overlayed recipes RFC
  68. still remaining: busybox and gst-ffmpeg bbappends, xserver-nodm-init
  69. => PRINC: issue warning now, error in 1.5, revisit before release (RP)
  70. => document PRINC - PR server migration steps (fray)
  71. => proposal: error and a disable flag, revise RFC patch (fray)
  72. RFC switching wholeheartedly to libav (bluelightning) sent, a few responses
  73. -> two bbappends left: gst-ffmpeg (bluelightning) and busybox (khem)
  74. also tslib (overlay), bluelightning pinging kergoth
  75.  
  76. c. python 3
  77. -> currently tackling 2.7.3 first
  78. probably 2.7.3 in 1.5, move to python 3 in 1.6
  79.  
  80. d. release status notification
  81. => maintain a wiki page to summarize release goals (jefro)
  82.  
  83. ___________________________________
  84. 5. infrastructure
  85.  
  86. a. oe.org flooded
  87. investigation underway
  88. Michael recommends Tom's approach, pushing users to mirrors
  89. invisibly enabling only actual committers to bang on master
  90. kernel.org follows this approach
  91.  
  92. ___________________________________
  93. 6. projects deferred
  94.  
  95. a. raise awareness of "janitor" list, QA "bugs"
  96. defer to after 1.4
  97.  
  98. b. document whitespace changes to the shell
  99. http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
  100. http://www.openembedded.org/wiki/Styleguide
  101. https://wiki.yoctoproject.org/wiki/Recipe_%26_Patch_Style_Guide
  102. => still need to de-dup these, need a volunteer
  103. ask for volunteers after 1.4 (jefro)
  104.  
  105. c. raise ntp with the Yocto Project [RP]
  106. immediate need addressed, reasonable default needed
  107. use LICENSE_FLAGS - non-commercial
  108. no default set after Paul's changes
  109. RP raised with YP AB
  110. => going to mailing lists & someone should write a proposal
  111. => fray will send to list after 1.4
  112.  
  113.  
  114. ________________________________________________________________
  115. Raw Transcript
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement