13:59:35 #startmeeting OPNFV TSC 13:59:35 Meeting started Tue Sep 8 13:59:35 2015 UTC. The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:59:35 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:59:35 The meeting name has been set to 'opnfv_tsc' 13:59:43 #topic Roll call 13:59:50 #info Chris Price 14:00:01 #info Uli Kleber 14:00:07 #info Julien 14:00:12 #info David Duffey 14:00:14 #info chenshuai 14:00:23 #info hongbo 14:00:33 #info Peter Bandzi (on behalf of Frank Brockners) 14:00:44 #info bryan Sullivan 14:01:40 #topic Approval of previous minutes of meeting. 14:02:01 #info Gerald Kunzmann (DOCOMO) 14:02:03 #topic Agenda bashing 14:02:15 #link https://wiki.opnfv.org/wiki/tsc Todays agenda 14:02:29 proxy for Ashiq 14:02:58 #info Dirk Kutscher 14:03:55 #info Wenjing Chu 14:04:09 #info Tapio Tallgren 14:04:13 #topic TSC & committer elections 14:04:27 #info two nominations have been received for TSC chariperson. 14:04:47 #info rpaik will open the voting which will be open until the 15th of September 14:05:10 #info Committer elections have required some clarification of the committer list 14:05:36 #info dlenrow 14:05:38 #info rpaik proposes to postpone the committer board election by one week to allow for the clarifications to be accomodated 14:05:42 #chair rpaik 14:05:42 Current chairs: ChrisPriceAB rpaik 14:06:04 #info rpaik will start the election process for the committers next week. 14:06:17 #info one nomination has been received, more nominations should be sent to rpaik 14:06:52 #info uli asks every-one to review the list and send comments to rpaik 14:07:20 #chair dneary 14:07:20 Current chairs: ChrisPriceAB dneary rpaik 14:08:07 couldn't this be done on gerrit or any other acces control system we use? 14:08:29 ... long term I mean 14:08:32 #info heather clarifies that the canonical committer list is stored in the INFO file in the project repositories 14:08:46 we now have a quorum 14:08:56 thanks ray 14:12:30 #info dneary expresses an intent to propose a change to the bylaws for future elections 14:12:52 +10000000, code is not the only coin of the realm 14:13:52 The metric needs to be contribution through Gerrit reviews (submission and participation), and may need to have some minimum bar to be a viable criteria. 14:14:33 #info Dave Neary asks in committer is not the right metric for election. It disenfranchises people who contribute to the project. OPNFV is not a source code project 14:14:52 #topic Managing the communities proliferation of project meetings 14:15:31 #info dneary states real time meetings are not a productive method to apply in open source projects. 14:15:53 #info dneary states an interest to see that he would like to see more of our activities done asynchronously. 14:17:20 #info dneary adds that many OPNFV meetings are not timezone friendly and can disenfranchise people 14:17:33 #info promotes the idea of moving away from weekly meetings 14:18:23 #info tnadeau adds that many meetings are also overlapping 14:18:38 #info tnadeau raises the challenge of trying to attend simultaneous meetings. Indicating IRC may be more effective for handling many OPNFV topics. 14:19:21 I got disconnected from GotoMeeting... 14:19:59 Why would IRC not be available to anyone? (idk who's talking) 14:20:04 lost the last 5 minutes. lost audio from GTM 14:21:02 now back 14:21:45 #info RayNugent adds that IRC may not be available to everyone (restrictions in some countries/companies) 14:22:23 #info Julien 14:23:17 in OPenStack we have weekly meetings for all projects and we use IRC only 14:23:42 We might want to ask why member companies (via he Board perhaps) refuse to let people participate in open source projects using open source tools - or worse, fire them. This seems "odd" to me. 14:23:46 so the question is whether we have issues with the real time aspect or the media we are using 14:24:37 I think weekly meetings help in keeping things moving and disussing issues the project is facing with 14:25:00 if we cancel these then people will do it in back channels as opposed to publicly 14:25:21 ... or just simply in a less organized way, which will be hard to follow and join for new comers 14:25:30 Tom, while that seems logical, practically speaking it's not feasible. Some issues are corporate, some are country issues. 14:25:31 dneary: ^^^ 14:26:07 My suggestion was to put a list of meetings together which we recommend to cancel, and then give people the opportunity to argue to keep their meetings 14:26:14 +1 ildikov 14:27:08 dneary: and in OpenStack we have also participants from China, so there should be a solution for IRC also 14:27:27 and OpenStack has %100 virtual meetings, right? 14:27:35 i think online meetings are sometimes required/preferred, but projects should provide meeting meetings, update the Wiki, etc... 14:27:44 Perhaps we can give the PTLs the "option" to go to IRC exclusively rather than create a conga line for the guillotine 14:28:22 the default for PTLs is that they MUST have an IRC-based meeting with optional audio, at a min. 14:28:29 that at least helps move the ball in the right direction 14:28:33 We need to let projects describe what the needs of their particular project is at this time for realtime meetings. Some projects are at early stages in which realtime meetings are beneficial or maybe essential. 14:28:35 GeraldK: I think we could try IRC only 14:28:42 i agree to Ildiko, already several projects are working mainly in back channels 14:28:46 also depends at what phase the project is... need meetings at start to get people on the same page, then need should drop off if we are doing the right things 14:29:04 ildikov, I take the point - there is definitely a risk of falling into a clique of people who work together but that happens with real-time meetings too 14:29:11 #topic Community lab Pharos integration and CI processes report/discussion 14:29:41 #info uli-k indicates activity is ongoing around the use of Pharos labs in octopus 14:29:57 Under the auspices of doing what we say, i am dropping the audio portion of the TSC call and will continue here on IRC. 14:29:59 #info uli-k states there is a need for representation for the pharos lab representatives in the pharos meetings. 14:30:05 dneary: without those meetings things will more easily fall apart IMHO and believe me, I'm not a meeting addict 14:30:29 ThomanNadeau, I will need help scribing.... 14:30:29 ildikov, We do have quarterly in-person sync points too through the hackfests 14:30:34 dneary: so I think we should more try to figure out how to do it better rather than don't do it at all 14:30:35 s not n... 14:30:43 E.g. As part of the committee cleanup effort for Copper I will propose that that the bi-weekly meeting we hold (lightly attended generally) be made on-demand. I'll let the project supporters weigh in on that for a week before a decision is made. 14:31:09 ildikov, And debra's release planning meeting, where she will track whether projects are on track or not 14:31:10 dneary: but travel is even less available than IRC 14:31:14 #info trevor_intel states pharos participation has been addressed as a secondary activity up until now. 14:31:25 ildikov, I agree 14:31:42 #info trevor_intel would like to see more community focus and direction around pharos planning and lab federation 14:31:52 Some projects will need meetings - they should be as needed, rather than regularly planned, IMHO 14:31:58 dneary: and Debra's meeting is for keeping the release together and for finding solution to impediments, for which the meetings can be used for 14:32:13 as a point of interest, there are free HTTP IRC clients so it should not be an issue to access IRC. 14:32:31 ChrisPriceAB: +1 14:33:01 #info uli-k requests all TSC members who have labs involved in Pharos should ensure the labs are represented in pharos 14:34:51 #topic OPNFV release, artifact discussion 14:34:53 ChrisPriceAB, Postpone 14:34:58 #info postponed until next week 14:35:04 #topic OPNFV Support review and next steps 14:36:39 ildikov, debra's meeting has a request/requirement to submit progress weekly in email, if people are doing that I think that may well be sufficient to align ppl inside projects 14:36:54 #info ChrisPriceAB notes that many requests/questions have been answered within a day by 2 people on the opnfv-users mailing list. This is probably not scalable. 14:37:26 GotoMeeting is treating me badly today, trying to re-connect -- we need to have more asynchronous meetings... 14:37:27 ildikov, I'm aware this isn't a simple topic, and there isn't one 100% right answer - I think we can mitigate the worst ills 14:37:34 dku, :-) 14:38:24 dku: yeap, I would prefer IRC too ;) 14:38:32 #info bryan_att adds that conversations/resolutions also need to be distilled somewhere 14:39:13 #topic Project creation review project ARMBand 14:39:25 dneary: I guess you will send info/follow up mails to the list, so let's continue the discussion there 14:39:26 IRC works for some level of note taking but I find greater value in the audio discussions 14:39:36 #info bob outlines the goal of ARMBand is to integrate and support the use of ARM in the Brahmaputra release 14:39:58 #link https://wiki.opnfv.org/project_proposals/armband armband project proposal 14:40:24 dku, try to dial in via phone. i also have issues with GTM today but phone line is quite good 14:40:40 #info the project has identified a number of OPNFV project they will need to work with including CI & deploy projects amongst others 14:40:56 #info the project also intend to integrate an ARM based lab into pharos 14:41:31 #info ramki asks if the scope is around servers or edge devices 14:41:45 #info bob answers primarily around servers at this point 14:44:48 debra - the conversations need to be transcribed anyways, so we keep accurate meeting minutes. 14:45:57 ThomasNadeau yes, agree. However the IRC only meetings miss some context of the conversations as people abbreviate in writing. 14:46:20 it is worth noting, we are time bound for Brahmaputra, thus if a project cannot make it they will need to participate in future releases. :) 14:47:30 #info Mike_Lynch 14:48:23 #info Uli requests to have committers updated under “Key Facts” section 14:48:32 #startvote TSC vote to create the ARMBand project? (-1, 0, +1) 14:48:32 Begin voting on: TSC vote to create the ARMBand project? Valid vote options are , -1, 0, +1, . 14:48:32 Vote using '#vote OPTION'. Only your last vote counts. 14:48:35 #vote +1 14:48:36 #vote +1 14:48:37 #vote +1 14:48:37 #vote +1 14:48:38 #vote +1 14:48:39 #vote +1 14:48:39 #vote +1 14:48:40 #vote +1 14:48:41 +1 14:48:43 #vote 0 14:48:45 #vote +1 14:48:50 proxy for cdub, who is in a plane 14:48:52 #vote 0 14:49:01 #endvote 14:49:01 Voted on "TSC vote to create the ARMBand project?" Results are 14:49:01 0 (2): dku, bjskerry 14:49:01 +1 (9): dneary, dlenrow, bryan_att, ChrisPriceAB, ThomasNadeau, Tapio_T, uli-k, julien_ZTE, Wenjing 14:49:13 ChrispriceAB - precisely. RE: projects committing 14:49:38 #topic Project creation review of the Pinpoint project. 14:50:48 #link https://wiki.opnfv.org/pinpoint/pinpoint_project_proposal pinpoint project proposal 14:52:49 #info the pinpoint project will focus on fault correlation on the OPNFV platform 14:55:50 #startvote TSC vote to create the pinpoint project? (-1, 0, +1) 14:55:50 Begin voting on: TSC vote to create the pinpoint project? Valid vote options are , -1, 0, +1, . 14:55:50 Vote using '#vote OPTION'. Only your last vote counts. 14:55:52 #info uli-k extends an invitation to others to join the project 14:55:52 #vote +1 14:55:53 #vote +1 14:56:09 #vote +1 14:56:10 #vote +1 14:56:14 #vote +1 14:56:16 #vote +1 14:56:17 #vote +1 14:56:27 #vote +1 14:56:33 #vote +1 14:56:54 #vote +1 14:57:05 #endvote 14:57:05 Voted on "TSC vote to create the pinpoint project?" Results are 14:57:05 +1 (10): dneary, dlenrow, bryan_att, ChrisPriceAB, pbandzi, ramki, Tapio_T, uli-k, bjskerry, Wenjing 14:57:44 #topic AoB 15:00:19 #endmeeting