[yocto-ab] Minutes: Yocto Project Advisory Board, 23 May 2012

[Osier-mixon, Jeffrey]

Yocto Project Advisory Board
23 May, 2012

Attendees:
Richard Purdie, Linux Foundation
Dave Stewart, Intel
Joe Kidder, Enea
Daniel, Enea
Philip Balister, OpenEmbedded
Steve Sakoman
Lieu Ta, Wind River
Tracey Erway, Intel
Davide Ricci, Wind River
Sean Hudson, Mentor Graphics
___________________________________________________________________
Agenda & Actions:

Hot topics:
- Introductions (Joe Kidder)
  welcome Joe

- Yocto Project branding
  branding & compliance discussion ongoing in Advocacy group
  Mentor & Enea to review what is there & comment
  branding document set for review at next AB meeting
  compliance document set for review at next AB meeting
  Joe to discuss terminology on advocacy list

General status:
- Engineering
  1.3 work progressing well

- Finance
  currently on track, some members still need to pay Q1 invoice
  contact Jefro with any difficulties

- Advocacy
  branding & compliance (see above)
  working on t-shirts for ELCE event early
  website redesign - driving ecosystem, could be good to create a video
  meetings relative to DevDay in Barcelona
  mascot before ELCE
  optalked to LF re release schedule - they are writing an article

- Community
  upcoming conferences: LinuxCon Japan, OSCON, LinuxCon NA, ELCE
  article placed on IBM developerWorks
  monthly article placed on Linux.com
  annual report coming soon

- Infrastructure
  DDOS attack at OSU, recovering
  Michael catching up on upgrades, long backlog of sysadm issues
  shoeleather looking for more participation

___________________________________________________________________
Raw notes:

Hot topics:
- Introductions (Joe Kidder)
at enea since 05 - element, high avail middleware
cto office, filling in for magnus until replacement
working with linux for 6 yrs
located in Boston

- Yocto Project branding
Tracey branding process, Dave compliance doc
T:
kicked off branding document, if use yocto logo need this much room etc
how to appropriately use the brand
referenced from compliance document
using agency with other folks
=> set for review at next AB meeting
compliance doc run through tech committee to tie logo, terminology to project
identify value of the brand relative to the project, how to support w/compliance
three key things to promote, technical methods for compliance
also needs legal intro, not sure if that affects how portrayed/downloaded
  needs to be PDF? LF decides
still working, needs another rev through advocacy group before finalizing

D:
compliance - intent is to have something to allow AB to have brand control
if have brand that has value, promise to people
BSP, other component should work together with yocto
consulting services, confidence level
don't want to be completely onerous, difficult to complete
consistency, compatibility, meets technical criteria
many discussions - now have draft on wiki
discuss draft - Sanil sent excellent comments that need to be integrated


T:
somethign that provides a benefit to being a member in the yp itself
none really called out explicitly on website
if folks using for personal reasons, not going to have a problem
this is really for commercial relationships
focus on alignment with goals of project
Bill brought up previously - may have group involved & integrated,
relationship from high level
PB: aligned didn't have a bin for a large company
T: good point
SH: interest in drivign companies to contribute financiall to proje
Steve & Philip good examples, anyone can contribute code - welcome & desired
still need for companies to put money forward to keep e.g. sysadmin employed
T: agree, possibly change language to reflect
RP: people ask, what is benefit of being member of project? one way to drive
SS: confused about appropriate category for what I do - BSPs for customers
  if go through list, think could answer yes for both categories, so
why one or the other?
RP: intent is to show stronger participation - YPowered stronger branding
  two terms carry different weights, mean different things as brand develops
DS: also, part to assign YPowered to projects, company is aligned
  possibly suggest that use of terms
  I have x layer powered, company is aligned
  can change definitions
JK: almost sounds like aligned for org, powered for product
DS: kind of the way it has worked out
SS: so could be both
RP: don't know how to reconcile - no problem with using both terms like this,
  but tricky questions to answer
SS: YPowered for org, commercial product, would benefit YPowered logo associated
  admit confusion
T: if developing BSP, e.g.
  need to function as project - encourages companies to become members
& contribute
SH: not mentor's position - have heard expressed at confs, confusion about
  why care about something like aligned/powered? large companies
  just want to use it, don't care much about being associated
  regardless of what we do with compliance doc, open project
  have to be very careful about trying to force financial side & not
force into issues
DS: agree, not intent - opposite, they say I'd like to get some mileage
  we say we have this brand, but need to do a few things to use the brand
  e.g. pony up resources, join AB
  if decide to call what doing YP, then we have a concern about brand dilution
SH: ultimately, most value from technical side is sense of compatibility
  if have soem set of criteria or tests indicate compatibilty, that is valuable
  from Mentor's POV helps us, sense of reliability of BSPs from TI, Intel etc
  can associate with that brand
  if try to munge all into compliance issue, may not be best served
  separate issues in document - registration etc - from more financial aspects
  want people to indicate compliance separtely from use of term
DS: partially agree - if people want to refer to YP, go for it
  but if want to use brand assets - logo, trademarks - need to follow rules
  belly up to bar a little bit
  small bar for small orgs, bigger for bigger orgs
SH: agree, use of trademark very clearly something expectation
controlled by project
  so expectation of participation on financial level
  trying to get at - talking compliance & compatibility
  maybe small companies do a layer, not a full distro like Mentor, WR
  want to serve that better, look at providing technical compatiblity check
  not sure how that impacts - still under discussion in advocacy group
RP: intent that aligned category covers some of that problem
T: anything changed?
SH: participation in advocacy group, hopefully some new faces
T: a couple of members have said starting to get requests that ref use
of YP as requirement
  behooves us to take advantage of opportunity to provide good service
to contributors
DS: to that end, said immediate need for this (Mentor, Enea products)
  set goal to be done in this may meeting, discussion going on longer
  suggest - feedback, love what Sanil had done sending comments in separate doc
  if someone wants to hack into wiki, risk of being reverted
  will also ask Intel folks to register some BSPs to see how it works for them
  could be pretty close - some folks obviously have product considerations
=> SH to review what is there & overall from mentor standpoint
=> Enea also
SH: timeline? someone made good point in advo meeting, not perfect first time
  but at least up/down vote at next AB meeting
LT: at last advo, more clear discussion this week
SS: think it's really close - much more clear to me, understand how
I'd use categories
JO: could vote between meetings
LT: think we should wait - vote on email ok preliminary, would rather
do in meeting
  sometimes people miss email
DS: anyone have heartburn with that timeline? [no]
TE: language will need legal review
SH: AB to give nod to go upstream to LF
LT: tentatively vote at next AB meeting
=> Jefro to agendize
TE: LF has also been working on piece for YP
  released 1.2, need some marketing
DS: reasonable to open discussion about alternative names (aligned, powered)
TE: most like term aligned, powered maybe doesn't fit well with ways to be used
  at intel, powered = making it run, stretch for yocto project
SH: looking for alternatives, may not get headway
JK: yocto-enabled?  (build appliance took over 24 hrs)
TE: like term "enabled"
JK: feels more like what I want - something to enable this processor
SH: likes it as well
=> JK to bring up on advocacy list

General status:
- Engineering
RP: progressing with 1.3, processed input from various sources
  prioritized, overall themes - main one is consolidation
  remaining bugs in certain areas, good opportuntity to address
  schedule is out there, working against it
  upgraded EGLIBC, compiler - patches appearing

- Finance
LT: slides
slide 3, some missing q1 payments - good graphic showing income vs expenses
SH: mentor - check didn't get issued, invoice went to wrong place
  better way to ensure quarterly invoices arrive at right place
JO: contact me with any issues
LT: slide 4 shows expenses YTD
TE: has some expenses not shown, may not be quite in the black

- Advocacy
TE: mulling over a few things, not brought up in advo meetings yet
  t-shirts for ELCE event early
  website redesign - drivign ecosystem, could be good to create a video
    that includes everyone on board talking about involvement in project
  meetings relative to DevDay in Barcelona
    interested in creating DD on multiple hardware, include corp sponsors
	more diversity in instructors
  mascot before ELCE
  talked to LF re release schedule - they will create & incorporate
    on linux.com, other sources
SH: recently approached by Rudi, auto linux summit
TE: went to japan last year w/intro on yp for auto summit
  well attended by GENIVI for overlap
  small but remarkably well attended in Yokohama - Toyota etc
  positioned as available for use
  project gained recognition within GENIVI & others
  automotive, ivi - something we should do, discuss positioning
=> agendize for advocacy team
SH: meta-ivi status?
RP: meta-ivi - progress & developments, not watching 100%
  biggest problem now is systemd issue, lots of passion from OE
  on to-do list for 1.3 to find way to integrate with oe-core
  made public around release time, but not advertised
  can announce as official part of 1.3
  now also created meta-systemd in conflict with meta-openembedded
  hoping to resolve soon
SH: keen interest in announcement of meta-ivi layer
RP: jefro putting together blog post
=> keep AB in loop on layers & announcements & coordinate
SH: brings up issue - as new layers added in, public announcements, coordinate
  meta-mentor

- Community
JO:
articles: linux.com (ongoing), developerworks
involvement: oscon, linuxcon (reminder to submit & let me know), elce,
possibly auto summit
metrics up on wiki, annual report soon

- Infrastructure
JO: ddos attack, no breach
RP:
halstead working through backlog of infrastructure issues
rearranging hardware & autobuilders
  changing base OS installed, moving hardware around
  bugzila upgrades, changing categories
  improving bug tracking metrics, automating
SH: shoeleather around since October, still extremely rudimentary
  dont have even minor influx of people going there
  personally approved all requests
  would be helpful to get suggestions on what to do to improve
  more members to go poke at it
  followup - getting some builds shipped to run against real hardware
  find problems along that path, end up improving usability of lab & project
  ok to direct michael to help?
RP: agree value is there, can't stress how overloaded Michael is on upgrades
  question of priorities
  might also talk to Saul, has been watching Michael's workload
  ping to discuss over next few months
JO: blog post, page on website
SH: Ciby Peuse working on shoeleather-lab
  mentor taking baby steps to become more involved
  contribs limited by number of people

--
Jeff Osier-Mixon http://jefro.net/blog
Yocto Project Community Manager @Intel http://yoctoproject.org