17:01:25 <vishnoianil> #startmeeting tsc
17:01:25 <odl_meetbot> Meeting started Thu Jun 16 17:01:25 2016 UTC.  The chair is vishnoianil. Information about MeetBot at http://ci.openstack.org/meetbot.html.
17:01:25 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:01:25 <odl_meetbot> The meeting name has been set to 'tsc'
17:01:47 <mohnish__> #info mohnish anumala
17:01:53 <vishnoianil> #info vishnoianil
17:01:55 <edwarnicke> #info edwarnicke
17:01:56 <gkaempfer> #info gkaempfer
17:02:00 <abhijitkumbhare> #info abhijitkumbhare
17:02:31 <dfarrell07> #info Daniel Farrell
17:02:58 <colindixon> #info colindixon
17:02:59 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-06-09-17.03.html last week's meeting minutes
17:03:05 <colindixon> #link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=47102#Agenda the agenda in it's usual place
17:03:17 <ChrisPriceAB> #info Chris Price
17:03:27 <ttkacik> #info Tony Tkacik
17:03:34 <vishnoianil> #chair colindixon
17:03:34 <odl_meetbot> Current chairs: colindixon vishnoianil
17:04:05 <colindixon> #action phrobb and dfarrell07 to drive forward tooling and planning for the next TSC election
17:04:38 <tykeal> on a jet plane?
17:05:06 <colindixon> #action phrobb and/or colindixon to start the mail thread to discuss fast and phased approach and carbon release planning
17:06:13 <colindixon> #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 (that is to figure out what projects might be related to what you want to do)
17:06:22 <colindixon> #Und
17:06:38 <colindixon> #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:58 <colindixon> #action vishnoianil to schedule a meeting to discussion the project categorization
17:07:03 <colindixon> #action colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
17:07:08 <colindixon> #action colindixon to send e-mail about possibly moving our documentation toolchain to ReStructured Text => Sphinx => Read The Docs, as opposed to using AsciiDoc => Asciidoctor, which has caused us some pain
17:07:16 <colindixon> #action phrobb add documentation for the process of project PTL election
17:07:43 <colindixon> #undo
17:07:43 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Action object at 0x28eee50>
17:07:57 <rovarga> #info rovarga for jmedved
17:08:04 <colindixon> #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:08:06 <rovarga> (sorry, IRC was acting up)
17:09:34 <colindixon> #topic TSC mailing list votes and discussions
17:09:46 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-June/005396.html Giuseppe Petralia as NetIDE committer
17:10:02 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-June/005394.html Danian Shi and Yaozi Yang as committers on FaaS
17:10:27 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-June/005377.html Additional questions in the Project Proposal Template
17:10:53 <colindixon> #topic events
17:11:01 <colindixon> #link https://www.opendaylight.org/global-events
17:11:22 <colindixon> #info OPNFV summit in Berlin next week with an OpenDaylight mini summit
17:11:46 <colindixon> #info hackfest two weeks from now in San Jose
17:12:30 <colindixon> #info preliminary acceptances should have been sent out for the OpenDaylight summit, please register if you got one, some more may be coming
17:13:28 <colindixon> #info CaseyODL asks for anyone who might want to do do a demo or presentation at the ODL booth at OPNFV summit, please contact him TODAY
17:13:43 <colindixon> #info CaseyODL would also like for volunteers to man the booth if you're around
17:14:03 <colindixon> #topic boron
17:14:15 <anipbu> #info We have merged the removal of YangParserImpl class (old YANG parser) in ODL projects (MD-SAL, etc)
17:14:17 <anipbu> #link https://lists.opendaylight.org/pipermail/release/2016-June/006840.html   <--- Status email regarding removal of YangParserImpl
17:14:31 <anipbu> #info The patch series for Neutron Yang Model Revision will be merged soon in one week or two after blocker bugs are resolved.
17:14:36 <anipbu> #link https://lists.opendaylight.org/pipermail/release/2016-June/006744.html   <--- Status email regarding Neutron Yang Model Revision
17:14:41 <anipbu> #link https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=1458306352   <--- Google Spreadsheet tracking impacted projects
17:15:00 <anipbu> #info The OpenFlowPlugin project will be changing the default design on the master branch from the old –he design to the new –li design on Tuesday.
17:15:05 <anipbu> #link https://lists.opendaylight.org/pipermail/release/2016-June/006858.html   <--- Status email regarding OpenFlowPlugin Li Design
17:15:22 <anipbu> #info odlparent team upgraded netty to 4.0.37 to resolve possible security issues that can lead to a DOS.
17:15:26 <anipbu> #link http://netty.io/news/2016/06/07/4-0-37-Final.html   <--- security bug-fix filled as CVE-2016-4970
17:15:30 <anipbu> #link https://git.opendaylight.org/gerrit/#/c/39978/   <--- Patch upgrading Netty
17:15:45 <anipbu> #info Boron M4 Offset 1 are due today 6/16/2016.  Projects should take a moment to send their status.
17:15:51 <anipbu> #link https://lists.opendaylight.org/pipermail/release/2016-June/006855.html   <--- Status Email Template
17:16:13 <anipbu> #info The Boron Autorelease job was failing to build vtnmanager-vsemprovider.  The VTN team has fixed the issue with patch 40319 and we are awaiting the results of a new build.
17:16:18 <anipbu> #link https://git.opendaylight.org/gerrit/#/c/40319/   <--- Patch fixing autorelease
17:16:30 <anipbu> #info Atrium and Eman are still not in autorelease.  Reminder that projects should build successfully in autorelease by M4.
17:16:45 <anipbu> #info Reminder that M5 is coming up and that is the suggested “line in the sand” for Boron Stable Distribution.
17:17:21 <zxiiro> #info autorelease submodule timeout during cloning bumped to 60 minutes due to slow network
17:19:01 <colindixon> #info we're expecting this to go away when jenkins and nexus move to the private cloud
17:19:59 <colindixon> #info rovarga says that Nexus has been causing merge failures, recently, presumably for the same reasons
17:21:09 <colindixon> #info colindixon asks if we can move production jenkins sooner than 6/25 (currently scheduled), but tykeal says no because we'd need to move 2.5 TB of information, which is hard
17:21:26 <colindixon> #topic stable/beryllium
17:21:31 <colindixon> #info nothing this week
17:21:47 <colindixon> #topic system integration and test
17:23:12 <colindixon> #info it seems pretty unlikely at this point it seems unlikely that there will be a stable feature in Boron because it needs to be done by 6/30 (offset 0 M5)
17:23:30 <anipbu> https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-05-12-17.00.html
17:23:58 <colindixon> #info colindixon asks why that's happening, jamoluhrsen comments that it's because we don't have stable features, colindixon asks why that's true
17:24:59 <colindixon> #info jamoluhrsen says nobody's made the effort to become stable yet, dfarrell07 says he feels like we just need one project to pioneeer it
17:25:24 <colindixon> #info vina_ermagan says that she feels like lispflowmapping would be there save dependencies
17:25:31 <colindixon> #info rovarga says it pretty much has to be odlparent
17:25:48 <colindixon> #action colindixon to reach out to skitt about making odlparent stable
17:26:28 <colindixon> #info vrpolak_ says that other things blocking are peformance and stablity tests for config subsystem as a well as experimental features in restconf
17:27:37 <colindixon> #topic autorelease stability
17:27:59 <colindixon> #info we expect boron and beryllium will be fixed, we'll find out sometime tomorrow
17:28:13 <colindixon> #topic infrastructure
17:28:35 <colindixon> #info we made modifications to timeouts for gerrit with autorelease to fix intermittent faliures
17:28:47 <colindixon> #info no major system-level changes, yet
17:29:30 <colindixon> #info we're now working to make sure the private cloud sandbox works right to make sure things go smoothly when we move jenkins into the private cloud on 6/25
17:30:03 <colindixon> #info tykeal says that they're working on making the public cloud available for bursting as well
17:30:54 <colindixon> #info CaseyODL says they're looking at maybe moving toward something on stackoverflow instead of our own ask.opendaylight.org, so bring up questions if you have them
17:31:04 <colindixon> #topic user groups
17:31:32 <colindixon> #Info if you run a user group, CaseyODL should have reached out to you about moving to some new kind of meetup system
17:32:25 <colindixon> #info w.r.t. stack overflow/ask.odl, the key new feature we seem to be seeking is basically e-mail to bulletin board portal
17:32:40 <colindixon> #action CaseyODL to add a TWS on ask/stack overflow
17:33:02 <colindixon> #topic OpenDaylight wiki indexing
17:33:18 <colindixon> #Info abhijitkumbhare asks how we can make more of the wiki searchable via search engines
17:33:56 <jamoluhrsen> +1 to fix the wiki noindex issue.
17:33:56 <colindixon> #info CaseyODL says they can enable specific pages manually if you would like, for now all links from the main page and the project lists should be searchable now
17:36:01 <colindixon> #info colindixon asks if there's a way we can manage the robot.txt more easily, e.g., as a file in a git repo somewhere that we could modify easily
17:38:23 <colindixon> #info rovarga asks if there is some what to make that a tag in the wiki itself, colindixon says that we haven't found a way to make it a whitelist instead a blacklist tag
17:38:41 <colindixon> #action CaseyODL to start a thread on how to better manage the list of whitelisted pages
17:40:25 <vishnoianil> #link https://www.opendaylight.org/project-lifecycle-releases
17:40:25 <colindixon> #undo
17:40:25 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x28eb550>
17:40:45 <colindixon> #topic project lifecycle states
17:41:11 <colindixon> #link https://www.opendaylight.org/project-lifecycle-releases vishnoianil asks if offest 0, 1 and 2 projects can all be core
17:41:45 <vishnoianil> https://www.opendaylight.org/tsc-policy
17:41:52 <vishnoianil> Singularity:  To the extent possible, there should be no overlap between the goals of the core projects and artifacts created by them
17:42:22 <colindixon> #info colindixon says that offsets technically can't impact the lifecycle state since offsets aren't mentioned in the lifecycle states, but as edwarnicke points out to be central to OpenDaylight, it's more likely that you'll be offset 0 than others
17:43:15 <colindixon> #link https://www.opendaylight.org/tsc-policy vishnoianil also asks how we plan do deal the signularity clause
17:43:46 <colindixon> #info rovarga says it will be dealt with on projects moving to core, edwarnicke instead suggests that the singularity clause is harmful
17:44:30 <colindixon> #action edwarnicke and/or colindixon to add a discussion of the singularity clause as a TSC mailing list thread or future topic
17:47:41 <rovarga> ChrisPriceAB: +1, that was my understanding
17:48:22 <ChrisPriceAB> Oops, damn can of worms...
17:49:14 <colindixon> #link http://www.merriam-webster.com/dictionary/singularity colindixon also notes that the definition of singularity doesn't really match the meaning we want
17:49:52 <colindixon> #topic TSC elections progress
17:50:20 <edwarnicke> #link http://www.oed.com/view/Entry/180179?redirectedFrom=singularity#eid <- a dictionary that actually believes words mean things ;)
17:50:59 <colindixon> edwarnicke: but puts it behinda  loginwall so I can't see the definition
17:51:21 <edwarnicke> colindixon: weird... I didn't login
17:51:40 <colindixon> #info phrobb and dfarrell07 met to discuss how we can run the condorcet elections we'd like to run
17:52:19 <colindixon> #info we're exploring tooling, but right now we've realized that web-based ones don't provie what we need
17:52:49 <colindixon> #info implementing the framework should be pretty easy with libraries for voting
17:53:00 <colindixon> #info we need a user-guide for voting, rather than our current developer guide
17:53:33 <colindixon> #info we also need to figure out the settings of the knobs in our framework, e.g., the represented groups and their sizes
17:54:43 <colindixon> #topic cookies
17:54:47 <colindixon> #endmeeting