[yocto-ab] Minutes: Yocto Advisory Board, 3-May-2011

[Osier-mixon, Jeffrey]

Hi everyone - these are my very raw minutes from last month's meeting, which
I apologize for not sending out earlier. This afternoon I will clean these
up, and will also send out a draft agenda for tomorrow's meeting, hope to
see you there.

- roll call & introductions

x        jdk at ti.com
x        wmills at ti.com
x        paul.anderson at windriver.com
x        john_cherry at mentor.com
a        ehouser at ti.com
•        hailara at ti.com
x        amy szeto ti
a        brad_dixon at mentor.com
a        dirk.hohndel at intel.com
x        lieu.ta at windriver.com
•        dcauchy at mvista.com
x        jgreen at mvista.com
a        nithya.ruff at windriver.com
x        david.c.stewart at intel.com
•        atul.bansal at timesys.com
x        richard.purdie at linuxfoundation.org
x        steve at sakoman.com
x        philip at balister.org
a        morvek at mvista.com
x        sean_hudson at dell.com
a        tracey.m.erway at intel.com
x        ed.nash at timesys.com

Agenda

x Status on prior action items
  // set up mailing lists
  // only works with http
  // dev.yp.org links are all broken
  // talk to brad about

- Recap from Collab Summit & ELC events
  // good job guys

- Yocto Project community metrics
  // set out metrics on wiki & post link
  // track commits - already a summary page on git repo

- Feedback on governance & charter discussions described above

- Yocto Project 1.1 planning results & schedule
  // 1.0.1 milestone on track for june release, freeze tending toward end of
may
  // look on wiki
  // migrate 1.0.1 info to own page from release criteria

- Planning for future events, upcoming conferences
  // focused on vancouver, looking for travel for prague

  sean: rehash, metrics, tighten up webpage - what is breadbutter of these
meetings? what to discuss?
  bill: want to see happen dont know proper way to move fwd
    message between poky vs oe-core
    RP partly technical issue - on OE side, agreements now in oe-core
    clear when looking at codebase what is poky, what is oe-core
    still some changes to make, need to roll out to users & message, website
    bill: writeup somewhere?
    RP: how to communicate to users? webpage? target
    had discussions on oe-core mailing list, oe-tsc list, decisions
    clearer on technical side, needs to be clearer to yocto stakeholders,
best forum?
    bill: accept anyw ay that moves fwd
    blog post articulating understanding - good unofficial way
    a chair is a chair
    want t oget clarity
    ed nash - happy to read & provide feedback, email or link
    RP // wirte up summary & send to this group
  bill: some issues we care about in TI, jason started bsp group,
    difficult to tell pulse on is this group starting to form, need shot in
arm
    how are each company spending engineering time
    tricky point - dont want to form cabal, want to make sure to take tiem
to do effort communic well enough
    to know what everyone is up to
    opportunity within group to make sure putting in & getting out as much
as want to
    RP: understands - schdule clear on what being worked on, other particp
orgs not clear
    dont know how can communicate internalloy or publicly, focuses
interested in
    helpful to understand where people coming from
    bill: got into plannin gphase late, coming up to speed on proper venues
    number of orgs incl ti, in 1st cycle lot of work to transition to align
w/yocto
    lots of owrk upstream at oe
    sitll want to exchange info to see what's going on
    dave: really like idea, challenges have as a cross-organiz team sharing
what doing,
    plans on sohrt term
    need guidance on how to share what doing now vs
    involvement as well as resources
    like anothe rpart of of intel tha tneeds to share what they are doing
    more interesting to get insight into what silicon guys are doing, to
communicate
    what if have 1-page roadmap, may not want to share with no ndas
    friends on call, but businesses compete
    dont know right answer
    bill: dont need too deep
    jason: have 1.1 feature list, isn't that collective worklist?
    bill: all wind river & intel, understand 1.1 may look that way
    know there are companies, have specific plans to help yocto but no on
page
    jason: internal meetings, requesting that ti add to tha tpage
usingtemplate
    follow same process
    we haven't pushed our plans into that 1.1 releaes
    right way is to put into 1.1 release
    dave: can offer to have julie sit down with & get started
    paul: several categories, some synchronous with 1.1 infrastructural -
core changes
    bsp development - planned on 1.0 or targeting 1.1 re hw support
    would love ot kinow plans
    can operate somewhat asynchronously
    some sync with core, some async, dont have to be centrally managed
    bill: goals in time period is koen restruc angstrom for oe-core, how
instersect yocto? on yocto page?
    ecosystem issue
    sep categories of activities assoc with yocto project by various
interested parties
    RP: useful page with various particip orgs can put down waht they are
trying to achieve
    e.g. angstrom on oe-core
    converging on oe-core is hopefully aim - page for each org?
    sean: suggesting each org page current yocto activities?
    rp yes
    general agreement
    phil:Z 1.1 more usable by more people with more BSPS, not a general
requirement on list,  importanat to do that
    rp page
    dave need something like that for intel specific stuff
    //1 page for each
    represent oe - phil can ask what people can do for fall
    sean: currently working on (status) plus wish list area fo rpeople to
make suggestions
    rp: already have aset of feature pages
    on that list can highlight features  from specific orgs
    sean: primary purposes for meetings, features specific to each company &
feedbak into tech side of community
    here something we are working on
    role of advisory board, trying to come up with set of high priority
requests to technical side (RP)
    include OE (phil)
    RP: that is one role
    sean : what oathers?
    RP: resource mgmt & communication issues beetween comapnies,
marketing/branding delegated to subgroup but
    AB keeps finger on overall pulse
    dave agrees, see results - report back
    business heartbeat at meeting
    dave: planning page, split out 1.0.1 is done
    RP: one more, facilitate communication in wider fashion between orgs,
tech leads
    == what does richard need? ==
    making sure there aren no barriers to participation
    dave: could use planning page & extend to org specific, place for
interest groups to coordinate
    // set up placeholders for subgroups & interest groups, new interest
groups category onj wiki
      bill suggesets right afer projects on main wiki page
    // write down how interest groups & subgroups work



- List people or organizations on Governance page?
- Is 1 hour long enough for meetings?

    warmed up after agenda done
  phil: openembedded ev call for members

Action items from previous meeting, status shown if known:

1 - Create mailing lists and infrastructure for AB, interest groups, and
administrative groups [Jefro]  - done
2 - Investigate methods for providing phone & IRC support at F2F meetings
[Jefro] - working
3 - Coordinate a F2F meeting around ESC-SV with phone support [Jefro]  -
done
4 - Post minutes and results publicly on yoctoproject.org [Jefro] - done
5 - Rename Steering Group to Advisory Board in all public places [Jefro] -
done
6 - Revise website materials to reflect AB decisions [Jefro] - mostly done
7 - Provide transparency on past and present contributions, future plans
[All]
8 - Form an Advocacy and Outreach/Communications administrative group
[Tracey, Nithya, Lieu] - done
9 - Form an infrastructure administrative group [Dave, Sean] - done
  want to involve build mesiters, get together offline

10 - Form a BSP interest group [Jason] - done
11 - Advise Maintainers to stick to major/minor release numbering, and to
drive to quality & features within a 2-3 month window - done
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto-ab/attachments/20110607/41f092d8/attachment.html>