16:57:25 #startmeeting 6/26/2014 TSC 16:57:25 Meeting started Thu Jun 26 16:57:25 2014 UTC. The chair is regXboi. Information about MeetBot at http://ci.openstack.org/meetbot.html. 16:57:25 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:57:25 The meeting name has been set to '6_26_2014_tsc' 16:57:39 #info dmm 16:58:01 #topic TSC members please #info in 16:58:08 #info regXboi 16:58:20 * regXboi looks for chair volunteers :) 16:58:37 Phil won't be here this week 16:58:39 dmm: do you have audio? 16:59:09 I'm on the OPNFV call; give me 5 16:59:13 ah, k 16:59:14 thx 16:59:14 ah.... 17:00:28 #link https://wiki.opendaylight.org/view/TSC:Main 17:01:14 #link https://meetings.webex.com/collabs/meetings/join?uuid=MA3SRND964PIX06V2LS3SXX3RE-9VIB - webex link 17:01:45 edwarnicke you linking without infoing? 17:02:26 #info Kent Watsen 17:03:06 #info Ed Warnicke 17:03:34 #info Chris Price Joined 17:03:40 #info no phil today - recording started 17:04:48 hola 17:05:11 #topic creation review : TCP-MD5 17:05:29 regXboi: since you’re phil today,d o you want me to scribe? 17:05:40 #info delaying this to next week to ensure the two week period 17:05:53 #link https://lists.opendaylight.org/pipermail/project-proposals/2014-June/000145.html 17:06:04 #info Rob Dolin proxy for Rajeev Nagar (MSFT) 17:06:17 #info above link is TCP-MD5 email to project-proposals list 17:06:22 #chair colindixon 17:06:22 Current chairs: colindixon regXboi 17:06:26 colindixon: thanks 17:06:37 #topic scala discussion 17:06:45 https://lists.opendaylight.org/pipermail/project-proposals/2014-June/000145.html 17:06:50 FYI I'm here (and on the phone) for the IT repo bits... 17:07:07 #link https://lists.opendaylight.org/pipermail/discuss/2014-June/002695.html 17:07:14 #link https://lists.opendaylight.org/pipermail/discuss/2014-June/002880.html 17:07:45 #info links are start of use of scala discussion 17:08:29 #info the people looking to use Akka to build clustering originally wanted to use Scala to provide the clustering (as Akka is written in Scala) and they asked if that would be OK 17:08:46 #link https://lists.opendaylight.org/pipermail/discuss/2014-June/002880.html - comprimise 17:10:11 edwarnicke: thanks 17:11:52 #info question about how to capture a community decision 17:12:15 +1 for a formal way to record decisions with some context and background so things are revisited all the time. 17:12:31 #info that is ... the scala discussion comes to a question about how to capture a community decision 17:12:57 #info other examples of recording policy include: (a) checkstyle policy, e.g., trailing whitespace and (b) branching policy 17:13:09 #info colindixon thinks it is a good idea to have some way of recording decisions 17:13:27 #info edwarnicke talks about a possibility of using branching 17:13:44 is that kwatsen? 17:13:44 …I don’t think that’s what he was suggesting 17:13:48 yeah, I’m pretty sure 17:13:55 regXboi: that's what webex said 17:14:19 #info kwatsen suggests a current project status wiki page 17:14:42 #info dlenrow points out that some projects are updating the project proposal page and that should be discouraged 17:15:09 #info edwarnicke agrees that updating the project proposal page isn't a good thing 17:16:24 #link https://wiki.opendaylight.org/view/CrossProject:Documentation_Group example of the facts sidebox 17:17:17 #action colindixon to make the project "facts box" a wiki template 17:20:59 #topic TSC Charter Update 17:21:23 #info there is some more discussion about how to keep the actual list of projects synchronized over the varioius places they are listed, e.g., the main page, the helium release page, etc. 17:21:59 #info there is hope that having a template would help automate this assuming we make sure people us the template (the last two lines belong in the previous topic) 17:26:08 link to the options for all us not as much in the know? 17:26:20 #link https://lists.opendaylight.org/pipermail/tsc/2014-June/001309.html 17:26:33 regXboi: thx 17:26:38 dbainbri: trying to catch up :) 17:27:35 #startvote which charter language proposal to take to the board? 0 1 2 17:27:35 Begin voting on: which charter language proposal to take to the board? Valid vote options are 0, 1, 2. 17:27:35 Vote using '#vote OPTION'. Only your last vote counts. 17:27:35 regXboi: y, last i heard about this topic there were issues about any single company have more representation than others (i.e. unequal representation). not sure if that issue has been addressed. 17:27:39 dbainbri: Sorry about the inside baseball... hope the link helps :) 17:27:56 #info 0 means abstain 17:28:00 #info 1 means option 1 17:28:04 #info 2 means option 2 17:28:09 edwarnicke: thanks 17:28:13 #vote 1 17:28:16 #vote 1 17:28:19 #vote 2 17:28:33 #vote 1 17:28:41 #vote 1 17:28:51 #info dlenrow votes 1 17:28:56 #endvote 17:28:56 Voted on "which charter language proposal to take to the board?" Results are 17:28:56 1 (4): dmm, edwarnicke, kw_, ChrisPriceAB 17:28:56 2 (1): regXboi 17:28:57 #vote 1 17:29:08 #info RobDolin also voted 1 17:29:25 #info total (due to #infos) were option 1: 6, option 2: 1 17:29:33 @regXboi - No worries; I'm good with result :) 17:29:40 #agreed send proposal #1 to board 17:30:07 #info question: should both charter and bylaws be modified? 17:30:31 #info answer: the vote above only covers the charter 17:35:16 #agreed to take the charter language modifications to the board with the recommendation that the by-laws be modified in accordance with the charter modifications and intent 17:36:25 #action kwatsen to send dmm fully-updated charter/bylaw docs 17:36:36 thanks kw_ 17:36:49 #info Lenrow 17:37:09 just for future reference if you #action with your actual IRC handle being listed there, it will appear as assigned to you in notes at the end 17:37:18 #topic helium packaging 17:37:44 #info pen is turned over to sombody 17:38:14 #chair edwarnicke 17:38:14 Current chairs: colindixon edwarnicke regXboi 17:40:54 lenrow: welcome 17:41:41 dmm time management FTW! :) 17:41:44 #info return to topic of discussing ‘pure karaf’ 17:42:34 Happy Canada day to those celebrating on Tue, 7/1 ;) 17:42:50 :D 17:43:22 #info unclear how much will be accomplished based on the "swiss cheese" of next week 17:43:26 #link https://wiki.opendaylight.org/view/Tech_Work_Stream:Main#Upcoming_Meeting_Agendas future topics for TWS calls are listed here 17:43:33 #info this might be one such topic 17:43:40 #topic helium status issues 17:47:10 #info proposal to have a mailling list other than discuss for release email so that projects don't have to sort through on discuss 17:47:14 so we would have a "release" list as opposed to a specific version release list? 17:47:24 that's what I would suggest 17:47:52 or maybe just tag messages in the subject [release][foo][bar] so people can better filter? 17:47:55 dbainbri: already went there :) 17:48:29 release list with topics set... 17:49:21 I believe the list could be set to require topics 17:49:25 #info I am favor of a single release list 17:51:24 #info no disagreement with a single release list 17:51:29 #info HP will present our OF1.3 plugin architecture/implementation and demo it running on ODL on Monday TWS Call 17:52:29 sounds like an action for me... 17:52:37 #action tykeal to create a single release list 17:53:17 #action correction, regXboi to send email for creation of single release list to helpdesk 17:53:53 #topic it managed repository section in gerrit for holding sub-repositories 17:54:25 #info there have been requests for infrastructure pieces like Puppet, Jenkins Job builder, etc. 17:55:47 doh, I seem to have lost audio 17:55:56 #info request for a repository for holding this information with andy and aric as primary contacts 17:56:40 #info proposal from edwarnicke to have this be a project 17:57:48 #info tykeal considered that approach, but his thinking was that the outputs of this effort wouldn't be released as other projects released 17:59:44 #info more discussion about licensing 18:02:40 #info recommendation to tykeal to bring the idea to the mailing list along with a minimal form as an example 18:03:10 #info last note: US 0-1 GER, POR 2-1 GHANA 18:03:11 Thanks regXboi for operating the meeting. 18:03:17 #endmeeting