17:00:59 #startmeeting TSC Meeting 5-29-2014 17:00:59 Meeting started Thu May 29 17:00:59 2014 UTC. The chair is phrobb. Information about MeetBot at http://ci.openstack.org/meetbot.html. 17:00:59 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:59 The meeting name has been set to 'tsc_meeting_5_29_2014' 17:01:09 #info Madhu Venugopal 17:01:31 #chair regXboi 17:01:31 Current chairs: phrobb regXboi 17:01:44 coming :) 17:01:58 #topic TSC Members please #info into the meeting 17:02:10 #info regXboi still getting to webex 17:03:14 #help 17:03:15 #info Ed Warnicke 17:03:25 #info Lenrow Present 17:03:31 #info Madhu Venugopal 17:03:34 help 17:03:45 help? 17:04:46 #info Kent Watsen 17:05:00 #info Chris Price is here 17:05:17 #chair RobDolin 17:05:17 Current chairs: RobDolin phrobb regXboi 17:05:49 kwatsen: you can see a summary of meetbot commands here: http://meetbot.debian.net/Manual.html 17:05:55 and made it 17:06:02 #info Rob Dolin proxy for Rajeev Nagar (MSFT) 17:06:23 #topic Agenda bashing 17:06:37 #link https://wiki.opendaylight.org/view/TSC:Main 17:08:36 #info edwarnicke thanks auric and GiovanniMeo putting in weekly automated releases 17:08:50 #info Madhu points out this will be topic of next TWS call 17:09:08 #topic Event Updates 17:09:13 #info Chris Price would like to join the committee 17:09:28 * ChrsPriceAB for the SDN WC 17:09:30 #info phrobb asking for volunteers for program committies for upcoming events 17:09:36 #info TWS agenda for next week : https://wiki.opendaylight.org/view/Tech_Work_Stream:Main 17:09:45 #topic SFC to join Helium Simultaneous Release 17:10:35 #info paulq apologizes for not realizing that there is a separate item for joining Helium Simultaneous Release 17:10:47 #info phrobb asks if there are questions from the TSC 17:11:10 raises hand 17:11:44 #info Madhu has a question about whether it is possible for a new project joining now to join helium 17:12:34 #info ChirsPriceAB thinks that the TSC reserved the right to evaluate new projects on a case by case basis 17:12:44 #info phrobb concurs with that memory 17:13:10 #info RobDolin states this was written into the helium plan 17:13:28 #info Lenrow asks what are the dependencies of this module 17:13:51 #info ChrisPriceAB thinks there are dependencies going NB, but there are not dependencies going SB 17:14:03 #link https://meetings.opendaylight.org/opendaylight-meeting/2014/opendaylight-meeting.2014-04-17-16.56.html <— has reference to what was discussed for projects 17:14:07 #info Lenrow asks if this means there are no changes driven SB 17:14:33 #info ChrisPriceAB states there may be changes driven SB, but these need to be done in a backward compatible way 17:14:59 #info Madhu says his question is answered 17:16:28 #info more discussion of case by case 17:17:07 #info kwatsen says while he his is ok with this, the release plan should be updated with information on how projects join a release 17:17:12 #info rmoats +1 17:17:49 (heh) 17:18:04 #info that should have been regXboi +1 to kwatsen's statement 17:18:19 #info question on whether we can close the door or not now 17:18:42 #info that q was from ChrisPriceAB 17:19:07 #info s/join a release/declare intent/ (on my statement captured by Ryan) 17:19:24 #info concern from RobDolin that closing the door would be exclusive 17:20:21 #info Madhu has concern with needing to gate to ensure quality of release 17:20:55 #info RobDolin understands the needs for a long tail but says the conversation at that point should be along the lines of the questions Lenrow asked earlier in the conversation 17:21:27 * tbachman hands RobDolin a pacifier ;) 17:21:32 * regXboi notes the 2-month old may have useful things to say! 17:21:50 #info phrobb asks if a vote is needed 17:22:10 #info regXboi asks if anybody has a reason not to let SFC into Helium 17:22:39 #chair ChrisPriceAB 17:22:39 Warning: Nick not in channel: ChrisPriceAB 17:22:39 Current chairs: ChrisPriceAB RobDolin phrobb regXboi 17:22:57 #chair ChrsPriceAB 17:22:57 Current chairs: ChrisPriceAB ChrsPriceAB RobDolin phrobb regXboi 17:23:01 #unchair ChrisPriceAB 17:23:01 Current chairs: ChrsPriceAB RobDolin phrobb regXboi 17:23:16 #agreed with no objections the TSC allows SFC into the Helium release 17:23:25 #topic TSC Charter Modifications 17:23:45 #link https://lists.opendaylight.org/pipermail/tsc/2014-May/001254.html 17:25:53 #info phrobb begins to explain the changes to the by laws and the TSC charter 17:26:14 #info these changes stemmed from the initial attempt to run an election of at-large committers 17:27:43 #info the TSC recommended that platinum members continue to be represented even if an at-large representative from the same platinum member company is elected 17:28:27 #info the board wanted to add language to remove the restriction at a particular point of time by the super majority of a board 17:29:02 #info so the process would be to first approve these changes to the bylaws and charter 17:29:35 regXboi: I think it was more "he board wanted to add language to remove the restriction at a particular point of time by the super majority of a board" so that it could be removed for this election. The idea being that its the 'right' governance as is, but that we may take a little while to get there in terms of community growth. 17:29:40 #info and then the board would follow on by voting to remove the platinum member restriction for the purposes of this election 17:29:49 #chair edwarnicke 17:29:49 Current chairs: ChrsPriceAB RobDolin edwarnicke phrobb regXboi 17:29:59 #question: Could we get the actual language before and after on the IRC channel? 17:30:00 edwarnicke: you can help :) 17:30:29 #info Madhu asks if the at-large committers could potentially be from the same company 17:30:45 regXboi: Have I been chaired? 17:32:41 #info Proposed amendments are attached to an email sent by probb@linuxfoundation.org on Mon, 5/19 around 3pm (USA Pacific time) 17:33:16 so was the original restriction to prevent a single company to have much say on the TSC? 17:35:48 dbainbri: pretty much 17:36:32 so if this was a concern originally, why is this no longer a concern? 17:37:29 dbainbri: good question :) 17:38:13 regXboi: the problem was that the original election failed because a lot of the nominees declined because of the step down provision of the language 17:38:27 dbainbri: Feel free to speak up on the call :) 17:39:50 #info dbainbri asked why this a concern 17:41:16 #info phrobb represents the original concern which was the at-large election didn't work 17:41:43 #info dbainbri asks why the restriction is not an issue anymore 17:42:07 #info phrobb explains more of the background (apologies, I can't keep up with the discussion) 17:42:19 * regXboi looks to the other chairs to help scribe! 17:43:51 #info phrobb explains that the waiver language was to avoid requiring changing the bylaws multiple times 17:45:17 I'm not hearing anything did I lose you? or can no one hear? 17:45:30 phrobb: you may have dropped 17:45:53 I'm going to dial back in 17:45:55 #info kwatsen was concerned about how the original issues were rpesented 17:46:14 #info robdolin tries to explain how the original issues were voting 17:46:30 phrobb: very hard to hear you 17:46:41 #info that was David Lenrow, not RobDolin, I think 17:47:13 @TBachman Thanks :) 17:47:22 :) 17:47:23 #info phrobb points out that the language is set up to allow for the restriction to be removed on a case by case basis 17:47:59 #info kwatsen claims that is not the case - the language for an existing member stepping down has been removed 17:48:56 <- Raises hand 17:48:56 #info phrobb agrees that the step down language needs to be reinstated 17:49:07 RobDolin: will get you in a second 17:49:17 Thanks Ryan 17:49:47 #info RobDolin suggests that if we are not agreeing on language, we should break this out to a subcommittee 17:50:00 #info edwarnicke agrees this would be useful 17:51:24 Please tell me that languaging is not in the dictionary 17:52:08 lenrow: lmgtfy.com 17:52:23 :) 17:52:40 #info madhu asks where language about preventing at-large committers from the same platinum company 17:52:56 #info phrobb refers to section 4, buillet 3 17:53:01 #info Phil Robb points-out that there is another section that suggests at-large seats must be from unaffiliated companies 17:53:04 #info bullet 3 17:53:39 #info edwarnicke points out that bullet 3 can be read to apply to the original election 17:54:44 #info dbainbri asked about affiliation 17:55:22 #info phrobb answer there is language (regXboi adds in that the language is in the by-laws) 17:57:57 #info Ed Warnicke suggests that we consider scoping the question to the languaging of previously agreed intent as a separate question from other questions being raised. 17:59:08 #info regXboi laughs hystericaly 17:59:21 * regXboi nice 18:00:08 #info Subcommittee volunteers: Ed, Kent, Phil, Rob 18:00:18 (And Ryan would volunteer if he had time) 18:00:32 #action edwarnicke RobDolin kwatsen phrobb to make a small committee to craft language edits in bylaws and tsc charter to bring back to tsc for further discussion at next week's tsc meeting 18:00:47 #info Chris Price suggests we need to determine when the right of Platinum member to appoint expires 18:02:39 #info Rob Dolin needs to drop off today's TSC ConCall and passes MSFT proxy to Ivan Wood 18:03:07 call dropped...be right back 18:03:14 #info Ivan Wood 18:03:34 #info Vice Chair discussion will be deferred until dmm is back 18:04:34 #info kwatsen wants to split the two issues because while elections can close quickly, the VC discussion is still ongoing 18:04:53 #info phrobb says the language can be split if needed 18:05:13 #info edwarnicke distinctly remembers that the VC discussion is still open 18:05:32 #info phrobb says the VC language was also for review and to further discussion 18:06:30 #topic OpenDaylight Security Analysis 18:06:37 #link https://wiki.opendaylight.org/view/CrossProject:OpenDaylight_Security_Analysis 18:09:58 #info kwatsen asks w.r.t. load time signature checking, where will the private key be located? what about 3P off-line projects looking to integrate 18:10:55 #info Madhu answers that signing can be done with various private keys and checked with public keys, with support for importing additional public keys for checking 18:12:03 #info edwarnicke states that he put some effort into figuring how to sign bundles that go into nexus and that's hard to do in a reasonable way. 18:12:10 #info Madhu asks to explain 18:12:32 #info edwarnicke points out that the jenkins build system has to sign the artifacts and that is non trivial 18:13:14 #info getting artifacts signed in jenkins in a secure and reliable way is non-trivial in an open source project and automated release processes 18:13:15 #info the problem is not with the mechanics of signing but with the opensource mechanics of signing 18:14:03 #info Madhu wants to sign the release bundles only before they are pushed into nexus 18:14:12 #info (I think that is) 18:18:17 #info regXboi notes that significant overhead may be added to the build/debug process with the addition signed bundles 18:20:18 #info regXboi notes "security is goodness", we need to manage the mechanics as to not add significant overhead or complexity to the developer community who doesn't know how this works 18:20:24 oops 18:20:50 apologies - I got cut off! 18:22:11 #info Madhu notes that SNAPSHOT creation would be done in with security turned off. Bundle creation for end user consumption would include security/signing to give end user peace of mind in what they are running. 18:22:32 #info ken beck takes both sides of the discussion 18:22:44 regXboi: bring on the tomcat 18:23:02 #info, security also introduces bugs/errors adding complexity to the debug environment. This needs to be recognized as well. 18:23:04 I presume you mean the https stuff? 18:23:09 yep! 18:23:11 (the major changes stuff) 18:23:27 OK cool... your statement was kind of hyperbolic (and honestly... I am the last guy who can give you a hard time about hyperbolic) 18:24:12 *sigh* I love Karaf... but we aren't there yet (and I have moved a lot of code to get us there) 18:24:54 #info discussion of karaf's remote management environment 18:25:09 #info madhu makes a point that some of these are available today 18:25:28 #info edwarnicke (personal statement) says that we aren't to karaf yet 18:25:49 #info madhu says we may need to enable the features in a non karaf enviro 18:26:13 #info edwarnicke also wants it noted he likes karaf and is (personal statement) supportive :) 18:26:28 #info +1s that :) 18:28:03 #link https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Helium_Release_Plan - OFplugin has TLS support on its roadmap 18:28:55 #link https://wiki.opendaylight.org/view/Openflow_Protocol_Library:Candidate_RELEASE_Plan_2014 - as does OFjava 18:40:38 #info regXboi wants to thank the team for their effort - this is all *goodness* and the only question (in my mind) is how to get from here to there! 18:40:59 #topic helium simultaneous release logistics 18:41:10 * regXboi looks at edwarnicke 18:41:33 #link https://wiki.opendaylight.org/view/Simultaneous_Release:Helium_Release_Plan#Simultaneous_Release_Developer_Meetings 18:41:33 #link https://wiki.opendaylight.org/view/Simultaneous_Release:Helium_Release_Plan#Simultaneous_Release_Developer_Meetings 18:41:43 #link https://wiki.opendaylight.org/view/Simultaneous_Release:Helium_Release_Plan#Per_project_Simultaneous_Release_Contact 18:41:54 #link https://wiki.opendaylight.org/view/Simultaneous_Release:Helium_Release_Plan#Cross_Project_Milestone_and_Release_Candidate_Reporting 18:48:18 #info discussion between Madhu and edwarnicke about getting this to work 18:48:39 #info edwarnicke points to people implementing controller integration jobs 18:50:40 #info these are integration jobs that trigger a build in a project every time there is a merge in another project you depend on 18:50:40 #link https://wiki.opendaylight.org/view/GettingStarted:Jenkins_Integration_Job_Setup 18:51:36 #info this is very useful to find other projects issues 18:53:56 #endmeeting