Advertisement
Guest User

Untitled

a guest
May 21st, 2013
96
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.58 KB | None | 0 0
  1. OpenEmbedded Technical Steering Committee
  2. 21 May 2013
  3.  
  4. Attendees:
  5. Koen (koen)
  6. Khem (khem)
  7. Fray (fray)
  8. Paul (bluelightning)
  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. 4. projects in progress - status
  20. a. oe-classic recipe migration status
  21. b. oe-core release
  22. c. meta-oe appends/overlayed recipes RFC
  23. d. 1.5 planning
  24. e. python 3
  25. f. release status notification
  26. 5. infrastructure
  27. a. mailing list moving to YP server
  28. b. oe.org flooded
  29. 6. projects deferred
  30. a. raise awareness of "janitor" list, QA "bugs"
  31. b. document whitespace changes to the shell
  32. c. raise ntp with the Yocto Project [RP]
  33.  
  34. ________________________________________________________________
  35. Agenda & Results
  36.  
  37. 1. pick a chair
  38. ___________________________________
  39. 2. new issues
  40.  
  41. a. role of the TSC
  42. (http://lists.linuxtogo.org/pipermail/openembedded-core/2013-April/038756.html)
  43. -> proposal: monthly IRC meeting to replace one of the bi-weekly TSC meetings, open to all
  44. => think about for next meeting
  45.  
  46. ___________________________________
  47. 3. lingering issues
  48.  
  49. ___________________________________
  50. 4. projects in progress - status
  51.  
  52. a. oe-classic recipe migration status
  53. need some documentation on right way to synchronize layer usage
  54.  
  55. b. oe-core release
  56.  
  57. c. meta-oe appends/overlayed recipes RFC
  58. -> still remaining: busybox and gst-ffmpeg bbappends, xserver-nodm-init
  59. => RFC switching wholeheartedly to libav (bluelightning)
  60.  
  61. d. 1.5 planning
  62. RP on sabbatical
  63.  
  64. e. python 3
  65. need to start informing people of it -now-..
  66.  
  67. f. release status notification
  68. => maintain a wiki page to summarize release goals (jefro)
  69.  
  70. ___________________________________
  71. 5. infrastructure
  72.  
  73. a. mailing list moving to YP server
  74. in progress
  75.  
  76. b. oe.org flooded
  77. => investigate YP hosting, kernel.org mirror (jefro)
  78.  
  79. ___________________________________
  80. 6. projects deferred
  81.  
  82. a. raise awareness of "janitor" list, QA "bugs"
  83. defer to after 1.4
  84.  
  85. b. document whitespace changes to the shell
  86. http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
  87. http://www.openembedded.org/wiki/Styleguide
  88. https://wiki.yoctoproject.org/wiki/Recipe_%26_Patch_Style_Guide
  89. => still need to de-dup these, need a volunteer
  90. ask for volunteers after 1.4 (jefro)
  91.  
  92. c. raise ntp with the Yocto Project [RP]
  93. immediate need addressed, reasonable default needed
  94. use LICENSE_FLAGS - non-commercial
  95. no default set after Paul's changes
  96. RP raised with YP AB
  97. => going to mailing lists & someone should write a proposal
  98. => fray will send to list after 1.4
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement