13:58:23 #startmeeting LFN TAC meeting 13:58:23 Meeting started Wed May 23 13:58:23 2018 UTC. The chair is rpaik. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:58:23 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:58:23 The meeting name has been set to 'lfn_tac_meeting' 13:58:57 #chair phrobb 13:58:57 Current chairs: phrobb rpaik 13:59:17 #info edwarnicke 14:02:25 #info Daniel Farrell 14:02:25 #info Andre Fredette 14:02:28 #info Frank Brockners 14:02:35 #info Rossella Sblendido 14:03:04 #info Xiaojun Xie, China Telecom 14:03:05 #info Ray Kinsella for Rajesh 14:03:15 #info Wenjing Chu 14:03:20 8 14:04:06 Anders Rosengren 14:04:19 #info Tapio Tallgren 14:04:27 #info Anders Rosengren 14:04:29 #info mazin gilbert 14:05:57 #info discussion on postponing the budget process discussion based on GB meeting summary 14:06:00 #topic governing board review 14:06:15 #chair kennypaul 14:06:15 Current chairs: kennypaul phrobb rpaik 14:07:03 #info on project induction document, questions were raised on separating lifecycle and induction process documents in the GB meeting 14:07:52 #info on TF induction, GB had no objections in March meeting rather lack of induction process document 14:08:42 #info Tim Irnich (IRC only for a few more minutes) 14:09:14 #info the delay in induction process document was causing things to stall in the TF community and GB members discussed conditionally accepting TF and the vote is in progress 14:09:52 #info Jason Hunt, IBM 14:10:06 #info Greg notes that major issue with not having a budget for TF (e.g. for events) 14:14:49 #info on TAC project representation in the GB, the general consensus was that increasing the GB size would be challenging 14:15:24 #info GB discussed dedicating time in GB meetings for TAC representatives to share the latest updates from each community 14:15:58 #info there was also a discussion on empowering budget decisions under certain threshold (TBD) 14:16:26 #info voting on this item is in progress as well 14:16:53 #info phrobb notes that voting results will be recorded/documented 14:20:28 #info suggestion for TAC to make a recommendation in the budget request threshold 14:21:13 #undo 14:21:13 Removing item from minutes: 14:21:20 #info suggestion for TAC to make a recommendation on the budget request threshold 14:22:23 #topic communication with GB and among projects 14:22:49 #info phrobb to summarize GB meeting discussions on a monthly basis 14:23:22 #info GB is also requesting getting visibility into release themes from each communities early in the release cycle 14:24:10 #info proposing fd.io and OPNFV to start in the June meeting 14:24:51 #info proposed ODL and ONAP at the July 18 meeting 14:27:15 #info discussion that there maybe a fair amount of effort to gather info from the community 14:28:02 #info phrobb is also proposing to provide monthly updates on LFN communities via email 14:28:25 #topic community process documents 14:29:12 #info edwarnicke notes that there was a fair amount of feedback in the past week 14:32:24 #link https://gerrit.linuxfoundation.org/infra/#/c/10103 14:34:58 #info discussion on the term "market place" as it is used in OpenStack ("community", "not being a king maker", etc. were other suggestions) 14:35:31 #info request for comments in the document 14:35:58 #info Wenjing notes that "one size does not fit all" is the phrase used in the principles document 14:40:03 #info Greg asks if TAC could play an active role in "recruiting" projects 14:40:51 #info recruiting recommendation would be targeted on areas where there are gaps that need to be addressed 14:40:59 #link https://gerrit.linuxfoundation.org/infra/#/c/10221/ 14:43:04 #info Greg suggests that TAC projects should not be allowed to operate with broken governance for a long period of time 14:44:29 #info discussion on how you define/measure diversity 14:46:27 #info suggestion to have a "glossary of terms" 14:57:29 #info discussion on scheduling additional meeting(s) to continue working on the document 14:59:10 #info pick a method to review all the docs and then schedule a follow-up meeting 15:00:35 #info helpdesk ticket exists for removing autocheck from docs 15:00:40 #info will discuss budget topic in 2 weeks 15:00:46 #endmeeting