17:00:20 #startmeeting tsc 17:00:20 Meeting started Thu Jun 23 17:00:20 2016 UTC. The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html. 17:00:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:20 The meeting name has been set to 'tsc' 17:00:27 #topic agenda bashing and role call 17:00:29 #und 17:00:31 #undo 17:00:31 Removing item from minutes: 17:00:36 #topic agenda bashing and roll call 17:00:42 #info colindixon 17:00:45 #info mohnish anumala 17:00:55 #info edwarnicke 17:00:59 #link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=47211 the agenda 17:01:04 #info abhijitkumbhare 17:01:22 #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-06-16-17.01.html last week's meeting minutes 17:01:22 #info jamoluhrsen 17:01:24 #info gkaempfer 17:02:08 #info vishnoianil 17:02:14 #info ttkacik tony tkacik 17:02:21 #link https://lists.opendaylight.org/pipermail/release/2016-June/006933.html thread on possible migration from AsciiDoc/Asciidoctor to ReStructuredText/Sphinx 17:02:36 #info Prem_ (for Chris Price) 17:02:50 #link https://lists.opendaylight.org/pipermail/odlparent-dev/2016-June/000398.html thread on trying to get stable features from odlparent (looking to carbon to have an actual stable distrubiton) 17:03:27 * dfarrell07 is watching on IRC 17:03:32 #action colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron? 17:03:33 #action colindixon to clean up documentation for the process of project PTL election and post it on the TSC page in the normal place 17:03:52 #action CaseyODL to add a TWS on ask/stack overflow 17:03:52 #action CaseyODL to start a thread on how to better manage the list of whitelisted pages 17:05:03 #action anipbu to follow up on removing the ancient org.eclipse dependencies in controller (and elsewhere?) 17:05:51 dfarrell07: should we leave this: #action phrobb and dfarrell07 to drive forward tooling and planning for the next TSC election 17:06:02 jamoluhrsen: are you #infoed in for dfarrell07 ? 17:06:02 colindixon: yes 17:06:10 #action vishnoianil, phrobb and abhijitkumbhare Need to think of better approach on how projects can be categorize in a better way, so that it can be helpful for users who wants to propose a project proposal and looking for all the relevant projects in that scope. This will be useful in broadly categorizing the projects, that can be used as a reference for next TSC elections. 17:06:11 #action vishnoianil to schedule a meeting to discussion the project categorization 17:06:17 #action phrobb and dfarrell07 to drive forward tooling and planning for the next TSC election 17:06:18 colindixon: yes, he is my poxy 17:07:59 #topic TSC maling list votes and discussions 17:08:16 #link https://lists.opendaylight.org/pipermail/tsc/2016-June/005377.html Addition questions in the Project Proposal Template 17:08:30 #link https://lists.opendaylight.org/pipermail/tsc/2016-June/005428.html Fast and/or Phased Planning for the Carbon Release 17:08:40 #link https://lists.opendaylight.org/pipermail/tsc/2016-June/005407.html Asking the Board to Remove the Singularity Principle 17:09:10 #link https://lists.opendaylight.org/pipermail/tsc/2016-June/005420.html [VOTE] Ryan Vail as a committer on Packetcable 17:09:47 #topic events 17:09:49 dfarrell07: go vote on that packetcable committer email 17:10:20 #info we have the ODL hackfest next week on WTh (6/29-6/30) 17:10:48 #link https://www.opendaylight.org/global-events events in the usual place 17:11:01 jamoluhrsen: ACK 17:11:07 #info colindixon asks if we wnat to have a TSC meeting next week on 6/30 17:11:18 jamoluhrsen: imho you can do it for this hour 17:11:52 #info colindixon says that his take is agendas have been light and and the key issues we would like to resolve, e.g., carbon planning, might be better resolved with in-person work than a TSC meeting 17:12:13 #info vishnoianil, edwarnicke, and abhijitkumbhare all say they wouldn't mind canceling it 17:12:39 #agree there will be no TSC meeting next week on 6/30/2016 17:13:22 #info the OPNFV summit and ODL mini-summit in Berlin is just wrapping up 17:14:02 #info edwarnicke says that it was really good, he was mostly focused on fd.io and fast data stack, but there were lots of people with lots of diverse areas 17:14:31 dfarrell07: anything to add 17:15:16 #info upcoming evnets include LinuxCon Japan (7/13) and LinuxCon North America (8/22) 17:16:34 #topic boron 17:16:47 #link https://git.opendaylight.org/gerrit/#/c/35505/ <--- Neutron Yang Model Revision has been merged. 17:16:54 #link https://git.opendaylight.org/gerrit/#/c/35892/ <--- OpenFlowPlugin Migration to Li Design Default has been merged. 17:17:01 #info https://wiki.opendaylight.org/view/Weather#NetVirt_VPNService_Migration <--- NetVirt/VPNService has scheduled a TWS session to discuss. 17:17:18 #info There are plans to upgrade ietf-inet-types@2010-09-24 and ietf-yang-types@2010-09-24 (RFC 6021) to ietf-inet-types-2013-07-15 and ietf-yang-types@2013-07-15 (RFC 6991) in the Boron release, with impact to lispflowmapping, sfc, topoprocessing, openflowjava, restconf, neutron, ovsdb, gbp, netvirt 17:17:50 #link https://wiki.opendaylight.org/view/Weather#Upgrade_ietf-.7Binet.2Cyang.7D-types_to_2013-07-15 <--- Weather item for upgrade of ietf-{inet,yang}-types 17:17:55 #link https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=778533050 <--- Google Spreadsheet Tracking dependency and impact to ietf-{inet,yang}-types upgrade 17:18:29 #info The Boron Autorelease job is currently failing to build intent-listeners. The NIC team has fixed the issue with patch 40259 and we are awaiting the results of a new build. 17:18:34 #link https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-boron/160/org.opendaylight.nic$intent-listeners/ 17:18:56 #info For M4 Offset 2, we are hosting an IRC meeting on Wednesday June 29th at 10:00AM Pacific Time Zone for new projects to ask questions about their M4 requirements. 17:19:01 #link https://lists.opendaylight.org/pipermail/release/2016-June/006936.html <--- M4 IRC Working Session 17:20:18 #topic stable/beryllium 17:20:31 #info Beryllium SR3 is scheduled for 7/28/2016 with a cutoff on 7/24/2016 11:59 UTC. 17:20:45 #link https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-beryllium/198/testReport/ <--- Beryllium autorelease test failures in bgpcep and controller. 17:21:14 #topic system integration and test 17:21:21 #info jamoluhrsen says nothing this week 17:21:26 #topic infrastructure 17:22:09 #link https://lists.opendaylight.org/pipermail/release/2016-June/006937.html outage for this weekend to move the last things to the private cloud 17:22:19 #info When: Saturday, June 25, 2016 @ 08:00 - 17:00 PDT (15:00 - 00:00 UTC) 17:22:54 #info while gerrit will be up, jenkins will be offline, so jobs won't trigger 17:24:33 #info colindixon asks if we should block merges, tykeal and others note that the next job will pick it up, so it's low risk 17:25:01 #info also the fact that veriy jobs won't run, will likely gate things, so that it's not a real risk 17:25:21 #info tykeal says that we have a new APAC time zone joining as a release engineer, who we will likely see at events sometime soon 17:25:45 #topic David Goldber as a committer on UNI manager 17:25:51 #link https://lists.opendaylight.org/pipermail/tsc/2016-June/005429.html 17:26:04 #link https://git.opendaylight.org/gerrit/#/q/owner:%22David+Goldberg%22+project:unimgr commits 17:26:19 #link https://lists.opendaylight.org/pipermail/unimgr-dev/2016-June/000148.html 4 +1 votes 17:26:25 #ink https://lists.opendaylight.org/pipermail/unimgr-dev/2016-June/000150.html 1 more +1 vote 17:27:11 #info that's unanimous +1s from all current committers 17:28:30 #startvote shall the TSC approve David Goldber as a comitter on the UNImgr project? -1,0,+1 17:28:30 Begin voting on: shall the TSC approve David Goldber as a comitter on the UNImgr project? Valid vote options are -1, 0, +1. 17:28:30 Vote using '#vote OPTION'. Only your last vote counts. 17:28:35 #vote +1 17:28:36 #vote +1 17:28:36 #vote +1 17:28:37 #vote +1 17:28:38 #vote +1 17:28:38 #vote +1 17:28:40 #vote +1 17:28:42 #vote +1 17:28:49 ttkacik: ? 17:29:09 #vote +1 17:29:16 #endvote 17:29:16 Voted on "shall the TSC approve David Goldber as a comitter on the UNImgr project?" Results are 17:29:16 +1 (9): mohnish__, gkaempfer, edwarnicke, colindixon, ttkacik, jamoluhrsen, Prem_, vishnoianil, abhijitkumbhare 17:30:30 #agreed David Goldber is now a committer on UNImgr 17:31:02 #info mohnish__ notes that UNImgr is seemingly a PoC project and do we have a way to do that, should it be in ODL form 17:31:04 #undo 17:31:04 Removing item from minutes: 17:31:06 #info mohnish__ notes that UNImgr is seemingly a PoC project and do we have a way to do that, should it be in ODL forge 17:31:35 #info people note that ODL forge doens't exist yet, and we've generally erred on the side of giving people projects if they want them 17:31:53 #info gkaempfer also notes that it's moving past being just a PoC in this case toward tigher integration with vCPE use cases 17:34:46 #topic removing "draft" status from committer promotion process 17:34:58 #link https://wiki.opendaylight.org/view/TSC:Main#TSC_Procedures_and_Processes 17:35:10 #link https://wiki.opendaylight.org/view/TSC:Main#Committer_promotion_process_for_contributors_.28Draft.29 this is a draft at the moment 17:35:21 #action colindixon to start a thread to remove the "draft" status from committer promotion process 17:38:04 #info vishnoianil and colindixon talked earlier about making sure that the community is aware that nominations are also a call for public comment and not just comment/votes from existing comments 17:38:31 #info edwarnicke says to be careful with tone, by saying it's a public comment period than asking for concerns 17:43:31 #info colindixon also notes our governance generally as a way of escalation from conversation within the community, to comitters/PTLs mediating it at the project level, to TSC mediating it when there are disputes within or across projects, to the board resolving things involving the TSC 17:43:49 #info we don't communincate this well, and it's not explicitly stated anywhere 17:44:14 Once this discussion is over - I wanted to bring up Dave Lenrow’s email: https://lists.opendaylight.org/pipermail/tsc/2016-June/005419.html. 17:44:54 #action colindixon to start a therad on language and ways to communicate it 17:44:59 #undo 17:44:59 Removing item from minutes: 17:45:09 #action colindixon to start a therad on language and ways to communicate escalation processes for disputes 17:45:21 #topic attendance of the developer design forum 17:45:54 #link https://lists.opendaylight.org/pipermail/tsc/2016-June/005419.html 17:47:10 #info phrobb said the intent was that anyone who is registered to attend the ODL summit, can also attend the design forum, and the commit was only required if you wanted to only attend the free design forum 17:48:40 #info in essence the goal was not to exclude people that actually wanted to participate, but to make sure we didn't get accidental registrations for what happened to be free (which happend in the past) 17:49:14 #inof phrobb said: the intent is "have a gerrit id, get in straight away. Don't have one, then tell us why you'd like to attend." 17:49:24 #info phrobb said: the intent is "have a gerrit id, get in straight away. Don't have one, then tell us why you'd like to attend." 17:49:40 #action phrobb or colindixon to figure out how to communicate this better as the registration site stays up 17:50:49 #Info colindixon notes that part of the problem is that this was surprising and happend without community involvment, establishing a clear policy for how registration is handled in the future with community involvement seems importnat 17:51:07 #action phrobb to work on having a policy for how attendence to desing forums works going forward with community involvement 17:51:15 #topic cookies 17:51:18 #endmeeting