#opendaylight-meeting: MD-SAL Interest call

Meeting started by colindixon at 16:01:20 UTC (full logs).

Meeting summary

  1. agenda bashing (colindixon, 16:01:25)
    1. the main topic today will presumably be bug scrubbing (colindixon, 16:03:19)
    2. https://lists.opendaylight.org/pipermail/controller-dev/2015-June/009557.html the mail I sent with links to bug scrubbing lists (colindixon, 16:03:45)
    3. rovarga_ says that during the clustering call there was a call for applications to let them know (and thus also to some extent this call know) what their clustering requirement work (colindixon, 16:05:59)
    4. catohornet says there were some topics from the past that haven’t been closed: (i) Beryllium planning, (ii) Migration from He to Li (and in the future Li to Be), and (iii) the impact of project spinouts (colindixon, 16:07:33)

  2. bug scrubbing (colindixon, 16:08:58)
    1. https://bugs.opendaylight.org/show_bug.cgi?id=3643 (hideyuki, 16:10:07)
    2. colindixon asks if we have the links for this in a better place than his e-mail (colindixon, 16:10:52)
    3. ttkacik says he can play with sharing his bugzilla filters (colindixon, 16:10:59)
    4. rovarga_ aska bout JIRA progress since it’s easier to share filters there, phrobb says he’s still negotiating if we have a non-commerical license by their rules (colindixon, 16:11:30)
    5. ghall_ asks how we figure out when/if to cherry pick things back to Helium (colindixon, 16:18:56)
    6. ttkacik says we dont have any formal process for this, it’s all ad-hoc (colindixon, 16:20:19)
    7. ghall_ asks if we want to track which branch things should go to in the scrubbgin, ttkacik says that multi-branch tracking is a lot easer JIRA (colindixon, 16:22:01)
    8. ghall_ assks what the WAITING_FOR_REVIEW means, rovarga_ it means the the fix is not yet merged, but still in code review (colindixon, 16:22:30)
    9. colindixon asks if we need a new state NEED_FEEDBACK or NEED_MORE_INFO state (colindixon, 16:23:36)
    10. rovarga_ and ttkacik say yes and that we should reach out to Andy/Thanh to have it added (colindixon, 16:24:43)
    11. ACTION: ghall_ to send the request to helpdesk to add the state and help figure out the name if need be (colindixon, 16:26:49)
    12. https://git.opendaylight.org/gerrit/#/c/22189/ for BUG-3643 (rovarga_, 16:27:03)
    13. https://git.opendaylight.org/gerrit/#/c/22189/ for BUG-3643 (rovarga_, 16:27:09)
    14. ACTION: phrobb to track topics for the design summit, in this case clustering requirements for apps (colindixon, 16:41:52)

  3. Beryllium planning (colindixon, 16:52:56)
    1. colindixon asks where Beryllium planning is happening? ghall_ asks about maybe using the deisgn summit (colindixon, 16:54:14)
    2. ACTION: colindixon to work on pushing the M2 deadline out past the design summit to allow for the design summit input into release plans (colindixon, 16:55:16)
    3. http://bit.ly/1JCoKaa ttkacik and rovarga_ say that current Beryllium planning is happening on the bug lists with appropriate target milestones (colindixon, 16:56:45)
    4. ghall_ asks if we have a way to collect project input and aggregate it into requirements and planning? e.g., is this the right meeting for that? (colindixon, 16:57:28)
    5. colindixon and ttkacik say that this call is the right venue for discussion (once the release is out), but untilmately they want to track things with bugs (colindixon, 16:58:38)

  4. He to Li and Li to Be migration (colindixon, 16:58:53)
    1. Li to Be will obviously be a Beryllium feature if we do it? (colindixon, 17:00:15)
    2. so far, it looks like He to Li will haveen in an Lithium SR if it happens (colindixon, 17:00:37)
    3. rovarga_ says we desperately need somebody to drive this to complete and he unfortunately cannot be the person to volunteer for that (colindixon, 17:01:30)
    4. https://bugs.opendaylight.org/show_bug.cgi?id=3160 this is the bug tracking He to Li upgrades (colindixon, 17:02:12)

  5. the scope of this meeting (colindixon, 17:02:16)
    1. colindixon thinks this meeting will continue to cover the new spinouts, others seem to agree (colindixon, 17:02:30)
    2. colindixon says that the only other thing, would be maybe trying to fold basic AAA features into this call as well to cover all of the OpenDaylight “core platform" (colindixon, 17:04:31)
    3. ACTION: colindixon to try to get more people to attend (colindixon, 17:04:38)


Meeting ended at 17:04:52 UTC (full logs).

Action items

  1. ghall_ to send the request to helpdesk to add the state and help figure out the name if need be
  2. phrobb to track topics for the design summit, in this case clustering requirements for apps
  3. colindixon to work on pushing the M2 deadline out past the design summit to allow for the design summit input into release plans
  4. colindixon to try to get more people to attend


Action items, by person

  1. colindixon
    1. colindixon to work on pushing the M2 deadline out past the design summit to allow for the design summit input into release plans
    2. colindixon to try to get more people to attend
  2. UNASSIGNED
    1. ghall_ to send the request to helpdesk to add the state and help figure out the name if need be
    2. phrobb to track topics for the design summit, in this case clustering requirements for apps


People present (lines said)

  1. colindixon (37)
  2. hideyuki (5)
  3. odl_meetbot (3)
  4. rovarga_ (3)


Generated by MeetBot 0.1.4.