#opendaylight-meeting: tsc

Meeting started by colindixon at 18:00:12 UTC (full logs).

Meeting summary

  1. agenda bashing and roll call (colindixon, 18:00:18)
    1. colindixon (colindixon, 18:00:30)
    2. Daniel Farrell (dfarrell07, 18:00:52)
    3. https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=38535 the agenda in it's usual place (colindixon, 18:00:52)
    4. https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-11-12-18.00.html last week's meeting minutes (colindixon, 18:01:14)
    5. ACTION: colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade from Helium to Lithium (for SR3) https://bugs.opendaylight.org/show_bug.cgi?id=3160 (colindixon, 18:01:36)
    6. ACTION: ttcacik and zxiiro to work on getting feature-level code coverage numbers (colindixon, 18:01:51)
    7. ACTION: rovarga, alagalah, mohnish, ttkacik, vishnoianil, ebrjohn, RPenno, abhijitkumbhare will try to draft a paragraph around the best practices including this discussion and feedback (to be gotten) from PTLS, they should also feel free to provide feedback around tools and technical solutions to help with upstream/downstream breakages (colindixon, 18:02:01)
    8. Chris Price (late) (ChrisPriceAB, 18:02:09)
    9. ACTION: LuisGomez to give an estimate for a drop-dead date on when we'd need to decide if we actually need a stable distribution (colindixon, 18:02:43)
    10. Greg here for Luis (ghall__, 18:03:20)
    11. dlenrow (dlenrow, 18:03:24)
    12. mohnish anumala (mohnish_, 18:03:46)

  2. next week's TSC meeting (colindixon, 18:04:13)
    1. no meeting next week because of Thanksgiving (colindixon, 18:04:21)
    2. edwarnicke (edwarnicke, 18:04:31)

  3. TSC at-large Elections (colindixon, 18:05:07)
    1. there are 3-4 threads on the TSC list around the platinum designate wavier, maturity, core-ness and TSC compositoin (colindixon, 18:05:44)
    2. jmedved (irc only) (jmedved, 18:09:13)
    3. to be clear, the board asked us (and them) to figure out a way to avoid continuing approving the waiver forever (colindixon, 18:10:00)
    4. so far, nobody has come up with a plan that seems to ague a way to credibly avoid having to renew the waive without getting rid of platinum designates (colindixon, 18:13:56)

  4. events (colindixon, 18:14:03)
    1. https://www.opendaylight.org/global-events (colindixon, 18:14:10)
    2. colindixon asks if we have dates/plans for design forum after Beryllium, phrobb says he's shooting for the first week of March in the Bay Area (colindixon, 18:16:06)
    3. phrobb notes that basically that means we can't slip our 2/18 Beryllium release date (colindixon, 18:16:24)
    4. KLuehrs says that at the MEF hack-a-thon actually resulted in UNIManager code being written, specifically a NETCONF interface (colindixon, 18:17:54)
    5. edwarnicke is slightly concerned about stacking the Design Summit so close to our Beryllium Release, not only because it means we *can't* slip, but also because he expects many devs to be recovering from the final push (edwarnicke, 18:18:04)
    6. phrobb asks for feedback about the ODL hackfest, it was small, only 7-8 projects vs. 50+ in Beryllium, and fewer attendees than normal (colindixon, 18:18:25)
    7. edwarnicke, I agree, I'll raise that next (colindixon, 18:18:46)
    8. abhijitkumbhare says that he thinks maybe having it at SFO airport might have cut down on the people from the bay area attending due to the drive (colindixon, 18:19:36)
    9. I agree, Burlingame was suboptimal as a location (edwarnicke, 18:19:55)
    10. ACTION: phrobb to poll the PTLs about hackfest attendance (colindixon, 18:21:12)
    11. some projects are remote, so hackfest locality is critical, as is a well-prepared agenda (rovarga, 18:21:54)
    12. f2f meetings are fine, but we need to gauge release planning and f2f is super useful for design -- but that requires some buy-in ahead of time (rovarga, 18:22:30)
    13. edwarnicke points out that there's an inside/outside problem where the people who are already on the inside derive less value these days than in the past, but we still desperately need ways for outsiders to find our way in (colindixon, 18:23:16)
    14. dlenrow, phrobb, and others note that colocation might have hurt with people attending OPNFV at the same time (colindixon, 18:24:15)
    15. davidmichaelkarr says he finds these things useful as an oustider trying moving in (colindixon, 18:24:40)

  5. Beryllium (colindixon, 18:25:11)
    1. six projects are missing their M4 status, they've all been notified (colindixon, 18:25:30)
    2. autorelease is failing to build integration because nic and vtn have been removed from autorelase for AD-SAL reasons, but not from integration, working to resolve that in one way or another (colindixon, 18:26:05)
    3. https://docs.google.com/spreadsheets/d/1Kfp5HVQGydNegEjp6dD2V3XsUnqpice0bysWbdxABA4/edit#gid=1862710416 Beryllium status tracking sheet (colindixon, 18:26:23)
    4. https://wiki.opendaylight.org/view/Weather#Current_Weather_Report weather (colindixon, 18:26:36)
    5. BUG-4322 : YANG 'default' statements is not being enforced caused issues, but they seem to have been resolved now (colindixon, 18:26:57)
    6. we're at 48 of 52 projects having moved to JDK8 (colindixon, 18:28:01)
    7. edwarnicke notes that (a) while we agreed that we would move to JDK8 as a TSC in Beryllium, it didn't make it into the release plan outlout, (b) we have a lot of third-party dependenceis and they day is coming when we will have to move for security reasons (colindixon, 18:29:13)
    8. https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-06-18-17.00.log.html#l-159 (dfarrell07, 18:30:19)
    9. rovarga adds that we likely need to move to JDK8 only to avoid combinatorial increases in testing involving both (colindixon, 18:31:44)
    10. https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-06-18-17.00.log.html#l-159 TSC vote on JDK8 (dfarrell07, 18:32:13)
    11. colindixon states that the 4 remaing projects are just a matter of merging patches (colindixon, 18:33:05)
    12. edwarnicke asks whether we're testing with JDK7 or JDK8 in integration (colindixon, 18:33:58)
    13. rovarga says he thinks it JDK7, we need to fix that (colindixon, 18:34:09)
    14. ACTION: jamoluhrsen to figure out how to start doing testing with JDK8 (colindixon, 18:34:23)

  6. stable/lithium (colindixon, 18:34:41)
    1. Luis believes that we're testing on JDK7 currently (ghall__, 18:35:01)
    2. there is a blocking bug in OpenFLow plugin with an e-mail thread, we will resolve the issue and the release will be dlayed (colindixon, 18:35:04)

  7. integration and test (colindixon, 18:35:26)
    1. the multipatch job is working, jamoluhrsen will post a wiki and e-mail (colindixon, 18:35:36)

  8. infrastructure (colindixon, 18:35:42)
    1. autorelease job for JDK8 is failiong because of not enough file descriptors (colindixon, 18:36:01)
    2. zxiiro is looking into the JDK8 autoreleas job failures (colindixon, 18:36:49)
    3. rovarga asks about JIRA, tykeal asks for him to open a tick (colindixon, 18:37:05)

  9. YANG IDE proposal (colindixon, 18:37:25)
    1. https://wiki.opendaylight.org/view/Project_Proposals:YangIDE the project proposal (colindixon, 18:38:21)
    2. https://lists.opendaylight.org/pipermail/project-proposals/2015-October/000372.html proposed on 10/28/2015 (colindixon, 18:39:36)
    3. davidmichaelkarr:goes through the project proposal wiki page above, basically it will provide an Eclipse plugin with the normal things, e.g., project management, syntax highlighting, syntax errors, semantic errors, etc. (colindixon, 18:41:41)
    4. other niceties like code folding, auto-wrapping comment/description items, etc. (colindixon, 18:44:13)
    5. diagram model editor for visual editing of the model (colindixon, 18:44:28)
    6. exporting to Yin as well as printable UML (colindixon, 18:44:34)
    7. maven integration, for using ODL's style of YANG import managmenet and exporting models using maven to others consume (colindixon, 18:45:08)
    8. non-maven integration to find other import sources that aren't packaged as maven dependencies (colindixon, 18:45:37)
    9. davidmichaelkarr notes that there is an exiting YANG IDE eclipse plugin that some people use (colindixon, 18:47:37)
    10. https://github.com/xored/yang-ide/ you can find the exiting plugin here (colindixon, 18:47:59)
    11. as far as davidmichaelkarr can tell, it was a one-time effort, based on maven targeting ODL to a large extent (colindixon, 18:49:00)
    12. davidmichaelkarr says from his perspective these tools are more targeting end-users, less ODL directly, with less complextity and more targeting people like the OpenConfig user base, it's based on pyang and not as much maven (colindixon, 18:50:02)
    13. davidmichaelkarr is looking to try to pull the best of both pieces in the long run, but starting with the AT&T code base that targets more end-user like people (colindixon, 18:50:42)
    14. davidmichaelkarr had poked at the NetIDE project (also an eclipse plugin) looking for more experience and help, got no responses (colindixon, 18:51:55)
    15. davidmichaelkarr is willing to try to push that on his own, but would love to get help from the community (colindixon, 18:52:10)
    16. colindixon and edwarnicke suggest maybe making all three resources committed be committers would help (colindixon, 18:53:36)
    17. anton ivanov asks if this will be part of a simultaneous release, davidmichaelkarr says his take is that's likely true (colindixon, 18:55:28)
    18. davidmichaelkarr agrees that off-cycle releases might be useful (colindixon, 18:57:08)
    19. colindixon asks if they really want the scope to say "No other ODL subprojects will depend on the YangIDE application." (colindixon, 18:57:24)
    20. VOTE: Voted on "shall the TSC move the YANG IDE proposal either in it's current form or with the changes of adding the 3 resources committed to committers and/or removing the "No other ODL subprojects will depend on the YangIDE application." from the scope?" Results are, +1: 7 (colindixon, 19:01:05)
    21. AGREED: the YANG IDE project is now moved to incubation (colindixon, 19:01:18)

  10. cookies (colindixon, 19:02:43)


Meeting ended at 19:02:50 UTC (full logs).

Action items

  1. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade from Helium to Lithium (for SR3) https://bugs.opendaylight.org/show_bug.cgi?id=3160
  2. ttcacik and zxiiro to work on getting feature-level code coverage numbers
  3. rovarga, alagalah, mohnish, ttkacik, vishnoianil, ebrjohn, RPenno, abhijitkumbhare will try to draft a paragraph around the best practices including this discussion and feedback (to be gotten) from PTLS, they should also feel free to provide feedback around tools and technical solutions to help with upstream/downstream breakages
  4. LuisGomez to give an estimate for a drop-dead date on when we'd need to decide if we actually need a stable distribution
  5. phrobb to poll the PTLs about hackfest attendance
  6. jamoluhrsen to figure out how to start doing testing with JDK8


Action items, by person

  1. abhijitkumbhare
    1. rovarga, alagalah, mohnish, ttkacik, vishnoianil, ebrjohn, RPenno, abhijitkumbhare will try to draft a paragraph around the best practices including this discussion and feedback (to be gotten) from PTLS, they should also feel free to provide feedback around tools and technical solutions to help with upstream/downstream breakages
  2. colindixon
    1. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade from Helium to Lithium (for SR3) https://bugs.opendaylight.org/show_bug.cgi?id=3160
  3. jamoluhrsen
    1. jamoluhrsen to figure out how to start doing testing with JDK8
  4. phrobb
    1. phrobb to poll the PTLs about hackfest attendance
  5. rovarga
    1. rovarga, alagalah, mohnish, ttkacik, vishnoianil, ebrjohn, RPenno, abhijitkumbhare will try to draft a paragraph around the best practices including this discussion and feedback (to be gotten) from PTLS, they should also feel free to provide feedback around tools and technical solutions to help with upstream/downstream breakages
  6. UNASSIGNED
    1. ttcacik and zxiiro to work on getting feature-level code coverage numbers
    2. LuisGomez to give an estimate for a drop-dead date on when we'd need to decide if we actually need a stable distribution


People present (lines said)

  1. colindixon (100)
  2. edwarnicke (17)
  3. dlenrow (14)
  4. odl_meetbot (9)
  5. ChrisPriceAB (8)
  6. phrobb_ (8)
  7. dfarrell07 (6)
  8. jmedved (5)
  9. rovarga (4)
  10. jamoluhrsen (4)
  11. mohnish_ (3)
  12. davidmichaelkarr (2)
  13. tykeal (2)
  14. ghall__ (2)
  15. abhijitkumbhare (1)
  16. phrobb (0)
  17. anipbu (0)


Generated by MeetBot 0.1.4.