#opendaylight-meeting: TSC Meeting 2014-02-27

Meeting started by phrobb at 18:01:07 UTC (full logs).

Meeting summary

    1. dmm (dmm, 18:01:33)
    2. Madhu for RedHat (Madhu, 18:01:56)
    3. Vijoy Pandy present (phrobb, 18:02:34)

  2. approval of last week's minutes (phrobb, 18:04:03)
    1. AGREED: minutes from last week accepted (phrobb, 18:04:18)
    2. Rob Dolin, proxy for Rajeev Nagar (Microsoft) (RobDolin, 18:07:56)
    3. question on a group to do interop work and collects and brings back learning (phrobb, 18:08:27)
    4. http://www.isocore.com/mpls2012/ event described by David Meyer (RobDolin, 18:13:51)
    5. Phil Robb suggests 11 Aug, 2014 as potential release date (RobDolin, 18:14:39)
    6. David and Vijoy like a time-based approach (RobDolin, 18:16:09)

  3. Release Date for Helium (phrobb, 18:16:14)
    1. question/concern brought on avoiding the chaos of code freeze not happening. We need to follow our own process better this time (phrobb, 18:17:45)
    2. question - if a project misses a milestone, are they off the Helium release? (phrobb, 18:19:44)
    3. Chris Price joined the meeting (chrisprice___, 18:22:04)
    4. ACTION: dmm to kick off a thread to discuss process and rigidity of adherence to release schedule, code freeze, etc (phrobb, 18:22:42)
    5. regXboi made it in (regXboi, 18:22:49)
    6. further discussion on release process management ensued (phrobb, 18:25:24)
    7. comment/concern raised on the amount of code brought into the code base in a recent, short period of time. (phrobb, 18:27:19)
    8. , comment on getting to and maintaining a solid foundation of code.. is our code base stable/solid enough now or should we have that as a strong focus for Helium? (phrobb, 18:29:11)
    9. comment on release schedule - Hydrogen should have one or two bug-fix minor releases… this helps with stability… Continued improvement on quality for Helium needs also to be a target (phrobb, 18:32:35)
    10. comment we need to focus on a better automated integration and testing infrastructure (phrobb, 18:33:16)
    11. while the integration team and help build out the framework, each project needs to invest in significant improvement in their QA/integration (phrobb, 18:34:27)
    12. several members express that stable/quality code is essential for user acceptance of OpenDaylight. It needs to be a priority (phrobb, 18:36:22)
    13. comment on openstack treatment of hypervisors…. class A has had more testing, class B less testing, etc… (phrobb, 18:38:14)
    14. comments ensued.. plugins cause the aggregate to only be as solid as the weakest link… class designations could work, but the complexity would be difficult (phrobb, 18:40:49)
    15. this will require more discussion for quality/stability (phrobb, 18:41:22)
    16. Should we do a "quality based" release schedule instead of a time-based one? (phrobb, 18:42:05)
    17. discussion continues on time/feature/quality issues for release process (phrobb, 18:47:35)
    18. ACTION: dmm and Madhu to write up a proposal on release structure/process for TSC and community review (phrobb, 18:51:48)
    19. comment made to keep two things in mind… improving process for projects heading to a release is important but improvement of QA/integration infrastructure also needed (phrobb, 18:53:05)
    20. ACTION: Carol Sanders to kick off discussion on how to improve QA and integration test suite project activities (phrobb, 18:54:20)
    21. ACTION: probb to get an OpenStack rep into TWS call to show automated integration and test infrastructure (phrobb, 18:56:22)
    22. question, if we use time-base release, can we have criteria available to evaluate a project to drop or keep a project for a simultaneous release? (phrobb, 19:02:59)
    23. consensus that "yes" that is needed. (phrobb, 19:03:13)

  4. Creation Reviews (phrobb, 19:03:43)
    1. request made for all project proposals schedule creation reviews (phrobb, 19:04:08)

  5. DLUX licensing change request (phrobb, 19:04:25)
    1. comments made that the DLUX project will be sharing code with OpenStack/Horizon more than the rest of the ODP project (phrobb, 19:05:43)
    2. question what are the unforeseen effects of this, and also, is the problem going to explode with too many licenses (phrobb, 19:07:14)
    3. comment made that the TSC is evaluating this for technical validity. (phrobb, 19:12:28)
    4. question to DLUX team on "how much cross project code flow is expected"? (phrobb, 19:17:10)
    5. once or twice per release cycle is somewhat expect but this is conjecture as we they haven't done it yet. (phrobb, 19:17:59)
    6. AGREED: TSC has consensus that the technical value of sharing code between horizon and DLUX is valid. (phrobb, 19:25:50)
    7. ACTION: probb to set up meeting with IP & Legal for this discussion (phrobb, 19:26:39)

  6. TSC at large elections (phrobb, 19:26:48)
    1. ACTION: probb to get nominations process moving with a end date of 3/14/2014 (phrobb, 19:28:18)

  7. Branding discussion (phrobb, 19:28:35)
    1. ACTION: probb to set up meeting on branding for when edwarnicke__ is back the week of 23/10/2014 (phrobb, 19:29:23)

  8. naming / renaming of OVSDB (phrobb, 19:29:38)
    1. ACTION: madhu to lead discussion on this at next TSC meeting (phrobb, 19:30:04)


Meeting ended at 19:30:14 UTC (full logs).

Action items

  1. dmm to kick off a thread to discuss process and rigidity of adherence to release schedule, code freeze, etc
  2. dmm and Madhu to write up a proposal on release structure/process for TSC and community review
  3. Carol Sanders to kick off discussion on how to improve QA and integration test suite project activities
  4. probb to get an OpenStack rep into TWS call to show automated integration and test infrastructure
  5. probb to set up meeting with IP & Legal for this discussion
  6. probb to get nominations process moving with a end date of 3/14/2014
  7. probb to set up meeting on branding for when edwarnicke__ is back the week of 23/10/2014
  8. madhu to lead discussion on this at next TSC meeting


Action items, by person

  1. dmm
    1. dmm to kick off a thread to discuss process and rigidity of adherence to release schedule, code freeze, etc
    2. dmm and Madhu to write up a proposal on release structure/process for TSC and community review
  2. Madhu
    1. dmm and Madhu to write up a proposal on release structure/process for TSC and community review
  3. UNASSIGNED
    1. Carol Sanders to kick off discussion on how to improve QA and integration test suite project activities
    2. probb to get an OpenStack rep into TWS call to show automated integration and test infrastructure
    3. probb to set up meeting with IP & Legal for this discussion
    4. probb to get nominations process moving with a end date of 3/14/2014
    5. probb to set up meeting on branding for when edwarnicke__ is back the week of 23/10/2014
    6. madhu to lead discussion on this at next TSC meeting


People present (lines said)

  1. phrobb (49)
  2. RobDolin (4)
  3. regXboi (3)
  4. odl_meetbot (2)
  5. dmm (1)
  6. Madhu (1)
  7. chrisprice___ (1)
  8. dbainbri (1)


Generated by MeetBot 0.1.4.