18:00:12 <colindixon> #startmeeting tsc
18:00:12 <odl_meetbot> Meeting started Thu Nov 19 18:00:12 2015 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
18:00:12 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:00:12 <odl_meetbot> The meeting name has been set to 'tsc'
18:00:18 <colindixon> #topic agenda bashing and roll call
18:00:25 <colindixon> TSC members please #info in
18:00:30 <colindixon> #info colindixon
18:00:52 <dfarrell07> #info Daniel Farrell
18:00:52 <colindixon> #link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=38535 the agenda in it's usual place
18:01:14 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-11-12-18.00.html last week's meeting minutes
18:01:36 <colindixon> #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
18:01:51 <colindixon> #action ttcacik and zxiiro to work on getting feature-level code coverage numbers
18:02:01 <colindixon> #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
18:02:09 <ChrisPriceAB> #info Chris Price (late)
18:02:16 <davidmichaelkarr> #info David Karr
18:02:20 <colindixon> #undo
18:02:20 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x2418650>
18:02:36 <colindixon> davidmichaelkarr: typically #info in is for TSC members only
18:02:43 <colindixon> #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
18:02:49 <davidmichaelkarr> colindixon: Got it.
18:02:58 <colindixon> davidmichaelkarr: not that we're not stoked to have you ;p
18:03:20 <ghall__> #info Greg here for Luis
18:03:22 <colindixon> edwarnicke: coming?
18:03:24 <dlenrow> #info dlenrow
18:03:46 <mohnish_> #info mohnish anumala
18:03:58 <colindixon> we have quorum
18:04:13 <colindixon> #topic next week's TSC meeting
18:04:21 <colindixon> #info no meeting next week because of Thanksgiving
18:04:31 <edwarnicke> #info edwarnicke
18:05:07 <colindixon> #topic TSC at-large Elections
18:05:44 <colindixon> #info there are 3-4 threads on the TSC list around the platinum designate wavier, maturity, core-ness and TSC compositoin
18:05:47 <dlenrow> edwarnicke: Wandering Software Dude doesn't know which holidays apply?
18:06:21 <edwarnicke> dlenrow: Wandering Software Dude is surprised *everytime* when nobody else shows up on a random Monday ;)
18:08:58 * ChrisPriceAB contemplates the concept that the platinum delegates may be nefarious in nature...
18:09:13 <jmedved> #info jmedved (irc only)
18:10:00 <colindixon> #info to be clear, the board asked us (and them) to figure out a way to avoid continuing approving the waiver forever
18:11:46 <edwarnicke> phrobb: colindixon Thank you for the clarity
18:11:58 <ChrisPriceAB> is it true we don't have maturity?  none? :('
18:12:49 <dlenrow> Having platinum designates avoids corporate arms-race to have highest bidder buy-up all of the TSC members :)
18:13:56 <colindixon> #info 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
18:14:03 <colindixon> #topic events
18:14:10 <colindixon> #link https://www.opendaylight.org/global-events
18:15:11 <edwarnicke> colindixon: I agree with your statement about a credible plan... but I think we *may* have the various pieces floating around that could be cobbled together for whatever degree of phasing we choose (won't know till someone does it :) )
18:15:20 <colindixon> edwarnicke: +1
18:16:06 <colindixon> #Info 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
18:16:24 <colindixon> #info phrobb notes that basically that means we can't slip our 2/18 Beryllium release date
18:16:56 <edwarnicke> colindixon: Is slightly nervous about stacking things that close
18:16:59 <edwarnicke> Sorry,
18:17:07 <edwarnicke> edwarnicke: Is slightly concerned abotu stackign things that close
18:17:54 <colindixon> #info KLuehrs says that at the MEF hack-a-thon actually resulted in UNIManager code being written, specifically a NETCONF interface
18:18:04 <edwarnicke> #info 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
18:18:14 <jamoluhrsen> +1 for getting value from hackfest last week.
18:18:25 <colindixon> #info phrobb asks for feedback about the ODL hackfest, it was small, only 7-8 projects vs. 50+ in Beryllium, and fewer attendees than normal
18:18:31 <jamoluhrsen> how many ODL'ers for the hackfest were sneaking in to OPNFV talks
18:18:46 <colindixon> #info edwarnicke, I agree, I'll raise that next
18:18:58 * colindixon is also watching the clock for davidmichaelkarr's creation review
18:19:36 <colindixon> #info 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
18:19:55 <edwarnicke> #info I agree, Burlingame was suboptimal as a location
18:21:12 <colindixon> #action phrobb to poll the PTLs about hackfest attendance
18:21:54 <rovarga> #info some projects are remote, so hackfest locality is critical, as is a well-prepared agenda
18:22:01 <dlenrow> My TSC chair can out-travel your TSC-chair
18:22:28 <colindixon> dlenrow: I realize that while I feel like I travel a lot, I don't int eh vast scheme of things :p
18:22:30 <rovarga> #info 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
18:23:16 <colindixon> #info 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
18:23:49 <ChrisPriceAB> I think colocation helps, but it was a tough time of year for travel
18:24:15 <colindixon> #info dlenrow, phrobb, and others note that colocation might have hurt with people attending OPNFV at the same time
18:24:40 <colindixon> #info davidmichaelkarr says he finds these things useful as an oustider trying moving in
18:25:07 <edwarnicke> phrobb: ChrisPriceAB whats particularly interesting is... I used to complain about collocating with only marginally related things... but in retrospect, I think we may have benefitted from that
18:25:11 <colindixon> #topic Beryllium
18:25:30 <colindixon> #info six projects are missing their M4 status, they've all been notified
18:26:05 <colindixon> #info 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
18:26:23 <colindixon> #link https://docs.google.com/spreadsheets/d/1Kfp5HVQGydNegEjp6dD2V3XsUnqpice0bysWbdxABA4/edit#gid=1862710416 Beryllium status tracking sheet
18:26:36 <colindixon> #link https://wiki.opendaylight.org/view/Weather#Current_Weather_Report weather
18:26:57 <colindixon> #info BUG-4322 : YANG 'default' statements is not being enforced caused issues, but they seem to have been resolved now
18:27:17 <colindixon> #lnk https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=1368787047 JDK8 migration tracking
18:28:01 <colindixon> #info we're at 48 of 52 projects having moved to JDK8
18:28:43 <edwarnicke> Which JDK is integration testing running with?
18:28:58 <edwarnicke> colindixon: Thank you for the data :)
18:29:13 <colindixon> #Info 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
18:30:19 <dfarrell07> https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-06-18-17.00.log.html#l-159
18:30:23 <dfarrell07> colindixon:^^
18:30:28 <colindixon> dfarrell07: thanks!
18:31:44 <colindixon> #info rovarga adds that we likely need to move to JDK8 only to avoid combinatorial increases in testing involving both
18:32:13 <dfarrell07> #link https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-06-18-17.00.log.html#l-159 TSC vote on JDK8
18:32:22 <edwarnicke> colindixon: To be clear... I checked because I'm not a huge fan of late breaking requirements...
18:32:38 <edwarnicke> colindixon: We may have to in this case, but I really really wanted it to have been an existing requirement ;)
18:33:05 <colindixon> #info colindixon states that the 4 remaing projects are just a matter of merging patches
18:33:58 <colindixon> #info edwarnicke asks whether we're testing with JDK7 or JDK8 in integration
18:34:09 <colindixon> #info rovarga says he thinks it JDK7, we need to fix that
18:34:20 <jamoluhrsen> colindixon, pound action integration group to move jdk8 for csit
18:34:23 <colindixon> #action jamoluhrsen to figure out how to start doing testing with JDK8
18:34:29 <phrobb_> Is there anything conceivabley possible that moving to JDK8 would affect apps built/running outside of ODL?... I.e. any tightly coupled end user apps that could rely on JDK7?... Is there some advance communication we would need to do there?
18:34:41 <colindixon> #topic stable/lithium
18:35:01 <ghall__> #info Luis believes that we're testing on JDK7 currently
18:35:04 <colindixon> #info there is a blocking bug in OpenFLow plugin with an e-mail thread, we will resolve the issue and the release will be dlayed
18:35:08 <rovarga> phrobb_: I think we should notify marketing and UAG ...
18:35:09 <jamoluhrsen> colindixon, would be nice to have confirmation from l2switch that their failures are the same bug
18:35:26 <colindixon> #topic integration and test
18:35:36 <colindixon> #info the multipatch job is working, jamoluhrsen will post a wiki and e-mail
18:35:42 <colindixon> #topic infrastructure
18:36:01 <colindixon> #info autorelease job for JDK8 is failiong because of not enough file descriptors
18:36:30 <phrobb_> rovarga, thanks, that's what I expected... I'll spread the word
18:36:49 <colindixon> #info zxiiro is looking into the JDK8 autoreleas job failures
18:37:05 <colindixon> #info rovarga asks about JIRA, tykeal asks for him to open a tick
18:37:25 <colindixon> #topic YANG IDE proposal
18:38:21 <colindixon> #link https://wiki.opendaylight.org/view/Project_Proposals:YangIDE the project proposal
18:39:36 <colindixon> #link https://lists.opendaylight.org/pipermail/project-proposals/2015-October/000372.html proposed on 10/28/2015
18:41:30 <colindixon> 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.
18:41:41 <colindixon> #info 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.
18:41:46 <jmedved> i can’t see ayhting shared
18:41:53 <colindixon> nothings's shared
18:41:56 <colindixon> just going through the wiki page
18:42:02 <jmedved> ack
18:42:19 <colindixon> are other people losing davidmichaelkarr for ~2-3 seconds every 30?
18:42:25 <phrobb_> ys
18:42:26 <phrobb_> yes
18:42:27 <mohnish_> yes
18:42:29 <colindixon> ok
18:42:36 <dlenrow> Q: Does this integrate with existing YANGtools code-gen, etc. or is it alternate example? Is visual editor or alternate way to generate ODL APIs from YANG files? Sits above yangtools?
18:42:43 <colindixon> given that he's just talking through what's there
18:42:53 <colindixon> I don't think it's a huge issue
18:43:15 <colindixon> dlenrow: under scope it says "The YangIDE application will use the Yangtools ODL subproject for parsing and semantic validation of Yang models. No other ODL subprojects will depend on the YangIDE application. "
18:43:20 <colindixon> dlenrow: does that help?
18:43:43 <dlenrow> Thanks. I need to learn this reading thing.
18:44:00 <phrobb_> I dlenrow  I muted you.. Please unmute when you need to talk
18:44:13 <colindixon> #info other niceties like code folding, auto-wrapping comment/description items, etc.
18:44:28 <colindixon> #info diagram model editor for visual editing of the model
18:44:34 <colindixon> #info exporting to Yin as well as printable UML
18:45:08 <colindixon> #info maven integration, for using ODL's style of YANG import managmenet and exporting models using maven to others consume
18:45:37 <colindixon> #info non-maven integration to find other import sources that aren't packaged as maven dependencies
18:45:41 <phrobb_> the audio  break ups are becoming more severe for me
18:45:42 * ChrisPriceAB finds David fades in and out, only me?
18:46:10 <colindixon> ChrisPriceAB: everyone
18:46:11 <dlenrow> phrobb: So you're not blaming me anymore ?
18:46:14 <jmedved> yes. still can decode what he wants to say :-)
18:46:28 <dlenrow> DIY sentence completion is entertaining
18:46:34 <phrobb_> I never blamed you... :-)
18:46:39 <phrobb_> dlenrow
18:46:41 <colindixon> ChrisPriceAB: he's just reading the proposal wiki page
18:46:50 <colindixon> so things are easy to fill in
18:46:57 <dlenrow> Colin thinks we can read
18:47:37 <colindixon> #Info davidmichaelkarr notes that there is an exiting YANG IDE eclipse plugin that some people use
18:47:59 <colindixon> #link https://github.com/xored/yang-ide/ you can find the exiting plugin here
18:48:08 * ChrisPriceAB enjoys DIY misinterpretation!
18:48:59 <edwarnicke> Is everyone else loosing about 5 seconds every 20 seconds or so?
18:49:00 <colindixon> #info as far as davidmichaelkarr can tell, it was a one-time effort, based on maven targeting ODL to a large extent
18:49:04 <colindixon> edwarnicke: yes
18:49:24 <abhijitkumbhare> I think david’s phone does not have a good signal
18:49:24 <edwarnicke> colindixon: It was done in two phases, but the moral point of your comment is correct
18:50:02 <colindixon> #info 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
18:50:16 <dlenrow> Can one vote +1/2?
18:50:42 <colindixon> #info 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
18:51:15 <dlenrow> I want to vote for the 1/2 that I heard
18:51:15 <colindixon> #chair phrobb dfarrell07 anipbu
18:51:15 <odl_meetbot> Current chairs: anipbu colindixon dfarrell07 phrobb
18:51:55 <colindixon> #info davidmichaelkarr had poked at the NetIDE project (also an eclipse plugin) looking for more experience and help, got no responses
18:52:10 <colindixon> #info davidmichaelkarr is willing to try to push that on his own, but would love to get help from the community
18:53:08 <tykeal> colindixon: I like to call it doughnut truck security
18:53:36 <colindixon> #info colindixon and edwarnicke suggest maybe making all three resources committed be committers would help
18:55:28 <colindixon> #info anton ivanov asks if this will be part of a simultaneous release, davidmichaelkarr says his take is that's likely true
18:57:08 <colindixon> #Info davidmichaelkarr agrees that off-cycle releases might be useful
18:57:24 <colindixon> #info colindixon asks if they really want the scope to say "No other ODL subprojects will depend on the YangIDE application."
18:59:21 <dlenrow> read edits into minutes and then vote?
18:59:29 * dfarrell07 wonders why it helps for this effort to be an ODL project. Are they thinking about CI infra? Community?
19:00:17 <colindixon> #startvote 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? -1, 0, +1
19:00:17 <odl_meetbot> Begin voting 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? Valid vote options are -1, 0, +1.
19:00:17 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
19:00:27 <colindixon> #vote +1
19:00:36 <dlenrow> #vote +1
19:00:41 <edwarnicke> #vote +1
19:00:42 <dfarrell07> #vote +1
19:00:43 <jmedved> #vote +1
19:00:45 <colindixon> to incubation is implied
19:00:49 <mohnish_> #vote +1
19:01:02 <ChrisPriceAB> #vote +1
19:01:05 * tykeal adds a work item to his list
19:01:05 <colindixon> #endvote
19:01:05 <odl_meetbot> 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
19:01:05 <odl_meetbot> +1 (7): dlenrow, jmedved, ChrisPriceAB, edwarnicke, dfarrell07, colindixon, mohnish_
19:01:07 <rovarga> davidmichaelkarr: congrats :-)
19:01:08 <dlenrow> Nice idea yangid
19:01:12 <ChrisPriceAB> phew that was close...
19:01:18 <colindixon> #agree the YANG IDE project is now moved to incubation
19:02:43 <colindixon> #topic cookies
19:02:50 <colindixon> #endmeeting