14:00:52 <ChrisPriceAB> #startmeeting OPNFV TSC
14:00:52 <collabot> Meeting started Tue Apr 14 14:00:52 2015 UTC.  The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:52 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:00:52 <collabot> The meeting name has been set to 'opnfv_tsc'
14:00:55 <Tapio_ta> #info Tapio Tallgren
14:00:58 <ChrisPriceAB> #topic roll call
14:01:03 <frankbrockners> #info Frank Brockners
14:01:04 <ChrisPriceAB> #info Chris Price
14:01:11 <ulik> #info Uli Kleber
14:01:12 <bryan_att> #info Bryan Sullivan
14:01:15 <ChrisPriceAB> #chair rpaik
14:01:15 <collabot> Current chairs: ChrisPriceAB rpaik
14:01:20 <cgoncalves> #info Carlos Goncalves (proxying Dirk Kutscher)
14:01:24 <Tapio_ta> #info Tapio Tallgren
14:01:26 <ChrisPriceAB> #chair bryan_att
14:01:26 <collabot> Current chairs: ChrisPriceAB bryan_att rpaik
14:01:36 <ChrisPriceAB> #chair dneary
14:01:36 <collabot> Current chairs: ChrisPriceAB bryan_att dneary rpaik
14:01:40 <bryan_att> I'm on IRC only today. Bin will be proxy for me if he can attend.
14:01:48 <dneary> Thank you ChrisPriceAB
14:01:59 <dneary> I will be distracted during today's call, not note taking
14:02:01 * ChrisPriceAB thanks bryan
14:02:33 <ChrisPriceAB> #chair ulik
14:02:33 <collabot> Current chairs: ChrisPriceAB bryan_att dneary rpaik ulik
14:03:08 <rprakash> #info prakash
14:03:32 <rajeev> #info Rajeev Koodli
14:03:47 <Ashiq> #info Ashiq Khan
14:03:53 <bin_> #info Bin Hu
14:04:03 <cdub> #info Chris Wright
14:04:10 <rprakash> #link https://wiki.opnfv.org/wiki/tsc
14:04:27 <hui> #info Hui
14:04:29 <julien_ZTE> #info Julien
14:04:50 <ChrisPriceAB> #topic Approval of previous minutes of meeting
14:04:58 <ChrisPriceAB> #agree approved
14:05:09 <ChrisPriceAB> #topic Agenda Bashing
14:05:56 <ulik> #info no project approvals today (remaining projects asked to be done next week)
14:06:22 <rprakash> #info opnf certification Heather to talk oday
14:06:50 <ulik> #info Frank asks for update from marketing about release marketing / message
14:07:07 <iben_> default open or closed for gerrit?
14:07:10 <rprakash> #info Frank asks for Release diagram staus from Marketing
14:07:11 <ChrisPriceAB> #info TSC budget allocation to hoodies and collateral
14:07:13 <iben_> can we add that to agenda?
14:07:22 <iben_> this is a policy decision
14:07:40 <ChrisPriceAB> #info open access to OPNFV materials
14:07:51 <Parviz> #info Parviz Yegani
14:08:02 <iben_> not just the ouput final materials - but to be open during the review process
14:08:37 <iben_> and - how to remove committers from projects if they have left teh role
14:08:52 <ChrisPriceAB> #topic committer promotions
14:09:08 <iben_> bad email address for example as the person left the company
14:09:21 <ChrisPriceAB> #link https://wiki.opnfv.org/developer/committer_promotions committer promotion process
14:10:57 <ulik> #info new committers must have shown contributions
14:11:18 <ulik> #info there must be a voting of committers in the projects
14:12:17 <ulik> #info Frank asks whether majority includes no-answer or abstain
14:12:34 <bryan_att> Uli, do you expect current committers also to have to provide contributions to remain as committers? What is the period for "good standing" tests?
14:12:44 <fdegir> and how long the voting is kept open?
14:13:19 <ulik> bryan: if committers don't contribute for long time, a PL can ask to remove them ....
14:13:30 <bryan_att> It should be an absolute majority. See Wikipedia.
14:14:10 <rprakash> #info PL PTL may have their biases too
14:14:46 <ulik> PTL cannot easily remove committers.
14:14:49 <bryan_att> I suggest we try not to create too many formal rules for project roles
14:14:52 <aricg> for example, http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-03-30-14.00.html
14:15:02 <aricg> its not clear if there was a majority vote, just that a vote happend.
14:15:40 <iben_> A Committer who is disruptive, or has been inactive for an extended period (e.g., six or more months) may have his or her Committer status revoked by the TSC. Project Leads must request the TSC for such an action to be taken.
14:16:57 <bryan_att> Iben, That's from the bylaws?
14:17:29 <dneary> Sounds like too much process for a young project.
14:17:53 <rprakash> #info Rajiv of Intel considers a week be given to vote in/out the commiters
14:18:18 <zhipeng> agree with dneary
14:18:42 <bryan_att> +1 to Dave also
14:18:58 <rprakash> #info quorum for voting needed eg. 6 of 10
14:19:20 <bryan_att> Quorum should not apply. Absolute majority.
14:19:29 <bryan_att> All committers must vote.
14:20:40 <dneary> It's a question of legitimacy: what is the possibility that a decision made by a subset of the committers will be considered illegitimate?
14:20:59 <dneary> If committers are inactive, they are not going to contest decisions
14:21:13 <dneary> If they could contest a decision, then by definition they're active
14:21:24 <ulik> #info people that are not active in gerrit don't need committer rights
14:21:25 <bryan_att> Dneary, it's just good form. Not a huge burden. Committers should be active and paying attention.
14:21:51 <dneary> Also, few projects do majority voting - there are always some votes which are worth more than others in an open source community.
14:21:52 <bryan_att> So they can be expected to vote.
14:22:09 <dneary> bryan_att, So if someone is inactive, his lack of a vote can be ignored
14:22:36 <dneary> I don't see why projects need quora, committer status, etc
14:22:46 <dneary> Just get stuff done
14:23:22 <bryan_att> Dave, I agree, but inattentive/inactive committers  should be removed as a committer. Lack of vote response should be an abstain.
14:24:42 <dneary> bryan_att, It's entirely possible to miss one vote or two
14:24:45 <ChrisPriceAB> #info TSC Charter description of committer removals:  A Committer who is disruptive, or has been inactive for an extended period (e.g., six or more months) may have his or her Committer status revoked by the TSC. Project Leads must request the TSC for such an action to be taken.
14:24:46 <dneary> And still be active
14:25:19 <bryan_att> Ok, then leave it up to the project to decide. I'm ok with that.
14:27:14 <dneary> bryan_att, I could agree with that
14:28:54 <ulik> #info Committer stand down is easier.
14:30:32 <zhipeng> +1 ulik
14:31:23 <bryan_att> Uli, can you drop a description of "stand down" into IRC? Not sure what you mean.
14:32:19 <ulik> #info Sorry for bad english. A committer might step down and voluntarily state he doesn't want to be a committer any more.
14:33:15 <iben_> yes - where is the clause in the charter where a committer has stated they will not be working with OPNFV anymore?
14:33:19 <bryan_att> ok, that's a common expression. Just wanted to be sure it was the conventional meaning.
14:34:17 <iben_> if they have left the company that signed the agreement with us then did not initiate a new agreement as an individual then they are not here
14:34:24 <iben_> they cannot be a member
14:34:49 <iben_> they should also be on the mailing list? That’s another way to check
14:34:55 <rpaik> For internal project decisions where no consensus can be reached, simple majority vote OF ALL Committers via +1 voting should be used.
14:34:59 <ChrisPriceAB> #action rpaik to propose updates to section 7 of the TSC Charter to clarify the intention of majority vote of comitters
14:36:07 <ChrisPriceAB> #agree that majority vote of committers intends to indicate a majority of all committers on a project are required to achieve a majority.
14:36:57 <ChrisPriceAB> #topic OPNFV Compliance & Certification Committee
14:37:03 <bryan_att> Chris, it would be good to use explicit terms, e.g. Simple majority or absolute majority.
14:37:19 * ChrisPriceAB yes lets capture that in the tsc charter
14:38:25 <ChrisPriceAB> #info heather outlines some discussions on the Board regarding any certification and compliance activities that have implications on OPNFV marketing.
14:38:46 <rprakash> #info Heather on  Thinking for Certificaton refer to what other Linux Destros have done
14:38:49 <rpaik> bryan_att it already says simple majority.  the confusion is whether it’s a simple majority of ALL committers (or a quorum)
14:39:02 <ChrisPriceAB> #info in other opensource communities a committee is implemented to govern this area.
14:39:35 <ChrisPriceAB> #info the Board, yesterday, agreed to instantiate such a committee in OPNFV to address the topic of compliance and certification.
14:39:58 <bryan_att> Ray, ok we will clarify that later. I'll email
14:40:03 <ChrisPriceAB> #info Heather asks for volunteers from the TSC to join the committee.
14:40:33 <iben_> Volunteers can be only from TSC?
14:40:37 <rprakash> #info Board has approved to review opportunities for certification and see how it can help if promote opnfv and request to form a committee to address it
14:41:30 <rprakash> #info certification committee of small number of people to scope technical details
14:42:41 <rprakash> #info OPNFV certification compliance committee - Board Member, TSC and Marketing team members only
14:42:59 <ChrisPriceAB> #info TSC members who are interested to participate in the committee should send an e-mail to heather.
14:43:18 <rprakash> #info send email to Heather and followup questions
14:44:07 <rprakash> #info Charter scope analyze what is that Certification involve and report back with recommendations
14:45:46 <rprakash> #info Keep it simple 2-Board 2-TSC 2-Marketing as composition and if more interest than revisit
14:46:18 <ChrisPriceAB> #topic Arno marketing update
14:47:07 <rprakash> #info Uli what you mean by no feedback
14:47:58 <ChrisPriceAB> #info heather outlines there is no further feedback on the diagrams since friday, all feedback thus far has been incorporated.
14:48:34 <ChrisPriceAB> #info as we have passed the deadline the current graphic is considered the final graphic for Arno (not available for presentation on the call)
14:48:43 <rprakash> #info most feedback on futures and some on slide 2  and 3-5 marketing is working on as graphics are not needed for web site fr now
14:48:43 <ulik> #info there was feedback to add documentation on Arno slide
14:49:28 <ChrisPriceAB> #info the slide outlining the futures is not considered final at this time.
14:50:13 <rprakash> #info Ray Nugent  wants to participate can volunteer and can work with Marketing team
14:52:33 <rprakash> #info Arno messaging by Marketing , TSC to review and Board to approve with proper verbage
14:53:09 <cdub> I have to leave, dneary is my proxy
14:53:36 <cdub> ChrisPriceAB ^^
14:53:46 <ChrisPriceAB> ok
14:53:52 <ChrisPriceAB> thanks :D
14:54:38 <tallgren> Can the interested parties join the Marketing mailing list?
14:54:44 <rprakash> #info Parviz asks if technical content on Marketing message is accepted by TSC
14:56:31 <rprakash> #info Parviz asks if TSC members need to give input , Ray Paik sent to tech discussions , once final version will be sent to TSC list too
14:58:02 <rpaik> #info Arno messaging/diagrams to be shared with the mailing list (for final technical sanity check)
14:58:02 <rprakash> #info Arno marketing  slide has tech content therefore a final check for technical accuracy is required by TSC members
14:58:59 <ChrisPriceAB> #topic Budget discussion on hoodies
15:01:10 <rprakash> #info 10k+ budget required for OPNFV huddies stickers like for OPenstack OPNFV day requires 300+ of these
15:01:16 <cgoncalves> Summer is comming. Hoodies may be too much and too costly when compared to tshirts :)
15:01:42 <bryan_att> +1 for shirts
15:02:44 <dneary> Speedos?
15:02:47 <bryan_att> Or hats
15:02:50 <dneary> Socks
15:03:11 * dneary likes the hoodies
15:04:15 * ChrisPriceAB lol dneary
15:04:56 <dneary> ChrisPriceAB, People keep making hats, t-shirts and hoodies, but no-one has given me pants yet
15:05:14 * ChrisPriceAB hehe, keep the web-cam aimed high!
15:05:38 <dneary> Seriously though:
15:06:11 <dneary> A higher cost but nice merchandise is fleeces or jackets - might be nice for that "community award" ideas
15:06:20 <dneary> Or laptop backpacks
15:06:35 <dneary> Smaller number, special item that not everyone gets
15:08:40 <bryan_att> How about OPNFV pen holders? Save your shirts and show your pride.
15:09:09 <rprakash> #info Frank Parviz Chris Dneary all are for quality and suggest that budget for Hoodies @23 for 400 is OK for Openstack
15:09:16 <zhipeng> Apple watch with OPNFV logo etched on it lol
15:10:06 <Yue> how about umbrella with OPNFV logo?
15:10:14 <dneary> ChrisPriceAB, The bikeshed should be red
15:10:27 * dneary is happy to move on
15:10:35 <cgoncalves> Yue: should be something that people could use during all year I'd say
15:11:00 * dneary is happy to have the board decide on the marketing budget, and the marketing committee to decide on how it should be spent
15:11:28 <RayNugent> Agree with dneary
15:13:15 <dneary> ChrisPriceAB, Thanks for the clarification. I'm happy to move on.
15:13:28 <rprakash> #info Hoddies are for developer community
15:14:35 <rprakash> #info Heather explains budget apportioning guidelines as Marketing team gets  from experts
15:16:16 <rprakash> #info 20% of the remaining budget now, hardware was one more major item used to day
15:16:26 <ChrisPriceAB> #agree to invest in OPNFV hoodies for the upcoming OpenStack summit.
15:17:18 <ChrisPriceAB> #topic  Open Access to OPNFV areas and tools
15:18:31 <rprakash> #info We can not access Gerrit without LF account - Iben
15:19:09 <ChrisPriceAB> #info iben outlines that the ability of external parties to review our patches and contributions is inhibited to extarnal parties.
15:19:46 <rprakash> #info it's a configuration  option, can some one take action item as Frank suggests
15:19:50 <ChrisPriceAB> #info dneary thinks this may be a configuration (or patch) issue in Gerrit
15:20:08 <rpaik> #action Aric to investigate if read-only aceess can be granted for gerrit
15:21:12 <rprakash> #info value creation is two way OPNFV  to upstream and vice versa as Frank mentions
15:22:57 <ChrisPriceAB> #agree OPNFV intends to be transparent and open for upstream communities
15:23:39 <rprakash> #info Changes may require lot of work to Gerrit for access change, even if its a read only access
15:24:06 <ChrisPriceAB> #action aricg to report back to the TSC with options for enabling open access to Gerrit.
15:24:28 <ChrisPriceAB> #undo
15:24:28 <collabot> Removing item from minutes: <MeetBot.ircmeeting.items.Action object at 0x1d77a50>
15:24:35 <ChrisPriceAB> #action aricg to report back to the TSC with options for enabling open read-only access to Gerrit.
15:24:56 <dneary> aricg, Is Gerrit using OpenID for LF, or really SSO (as in, if I log in to the wiki, I am logged in for Gerrit when I get there)?
15:25:28 <aricg> really sso
15:26:17 <dneary> aricg, OK - one option would be to switch to OpenID, and have id.linuxfoundation.org as the only trusted OpenID provider
15:27:10 <ChrisPriceAB> #topic Arno Project plans & tracking
15:27:15 <rprakash> #info tools need to have open access like wiki  for  Gerrit & Jira, open ticket for Aric to address when time permits
15:27:32 <ChrisPriceAB> #info RC1 report from frankbrockers
15:27:42 <frankbrockners> #link https://wiki.opnfv.org/releases/arno/releasecandidates_reports
15:27:58 <ChrisPriceAB> #info status updates on the wiki
15:28:18 <frankbrockners> #link http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-04-09-13.59.html
15:28:57 <ChrisPriceAB> #info minutes of the RC meeting
15:29:19 <ChrisPriceAB> #info due to delays in hardware availability RC1 was not fully passed
15:29:52 <ChrisPriceAB> #info deploy scripts and auto testing scripts are available in repositories now, documentation templates are now available.
15:30:16 <ChrisPriceAB> #info we are currently behind schedule, hope to catch up for RC2
15:30:43 <ChrisPriceAB> #info RC2 readiness.
15:31:18 <rprakash> #info LF hardware update
15:31:40 <ChrisPriceAB> #info LinuxFoundation hardware updates, last remaining item is to wait for adaptors to arrive.  (not confirmed to arrive yet)
15:32:41 <rprakash> #info Octopus readyness
15:33:22 <ChrisPriceAB> #info Fatih outlines that Jenkins connectivity to LF is pending, once ready it is expected that a one day lead time is required to have the jobs set up and connected
15:34:17 <rprakash> #info Fdegir says 1 day after Hardware setup to get Jenkins connects and run builds
15:34:53 <rprakash> #info Uli should Octopus release document be part of Release?
15:35:25 <iben_> we are moving forward with documentation for octopus and pharos
15:35:40 <ChrisPriceAB> #info octopus documentation is being worked on for jenking integration of additional labs.
15:36:01 <rprakash> #agreed that Octopus document will be part of Arno Release documentation
15:36:12 <ChrisPriceAB> #undo
15:36:12 <collabot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1e0a290>
15:36:16 * ChrisPriceAB not sure about that
15:38:41 <rprakash> #info add the details to wiki for documents
15:38:59 <ChrisPriceAB> #info BGS RC2 readiness
15:39:05 <rprakash> #info the adpater is coming today
15:39:34 <ChrisPriceAB> #info deploy script work is ongoing, foreman script is available in gerrit as of now
15:39:49 <ChrisPriceAB> #info pending target hardware for script validation
15:40:19 <ChrisPriceAB> #info functest RC2 readiness
15:40:31 <frankbrockners> sorry - GTM dropped me
15:40:38 * ChrisPriceAB ok
15:41:23 <ChrisPriceAB> #info scripts and structures in funcest repo are in place.  scripts being committed.  testing against target deployment pending previous CI/BGS actions
15:42:19 <ChrisPriceAB> #info intel lab access for Jenkins solved.
15:42:20 <rprakash> #info Intel LF connectivity is no more an issue
15:43:06 <ChrisPriceAB> #info RC2 readiness of opnfvdocs
15:44:04 <rprakash> #info templates and structures ready , pending for is for pharos & func test documentaion
15:44:47 <rprakash> #info RST format for release 1 doc for now
15:44:56 <iben_> need to get tokens to allow us to update the ARM with the PDF, HTML, and other outputs from OPNFVDOCS project
15:46:33 <rprakash> #info high risk on missing rc2 deadline so with rc2 it will be day by day folloups
15:47:48 <rprakash> #info requirements project Doctor no feedback
15:48:40 <rprakash> #info Two parts to release 1  - One for Tools and run times and other related to requirements
15:50:03 <rprakash> #info The release BGS-Octopus-Pharos-FuncTest  and others as Requirements to make platform better after Arno
15:51:07 <cgoncalves> ChrisPriceAB, HKirksey: thanks.
15:51:31 <rprakash> #info Parviz asking for release date - targeted for April 23rd and depending  on rc2 for now
15:54:36 <ChrisPriceAB> #topic Project Approvals
15:54:42 <rprakash> #info Heather talking to Analyst etc. so add your projects in wiki good details to refer to
15:55:47 <ulik> #info Chris clarifies that request for creation review must happen via an email to TSC.
15:56:19 <rprakash> #info tsc mailing list emails required for project creation review JOID (Juju track)
15:59:22 <rprakash> #info Bin Hui gives status on projects
16:01:25 <rprakash> #nfo community discussions around OSCAR and other projects required
16:01:58 <ChrisPriceAB> #endmeeting