Or iPhone one-tap : US: +16465588656,,190726272# or +16699006833,,190726272# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free) Meeting ID: 190 726 272 International numbers available: https://zoom.us/u/lWBuQ5ii
Summary of Airship Challenges and Future Plan (Sridhar Rao)
Vote: "Does the TSC exempt the Airship project from utilizing the Pod Descriptor File for the Iruya release based on a documented plan for supporting the PDF in the Jerma release? (+1, 0, -1)"
Discussion of OPNFV Strategic Objectives (Trevor Cooper)
Seeking input from OPNFV on 2019 goals - long term objectives and strategy. This is an on-going dialog - visit wiki page above to leave your comments
Have collected good feedback so far from individuals, please provide additional feedback to Trevor Cooper or add to the feedback Wiki page
SPC feedback page 2019 Goals - LFN SPC (note page name "2019 goals" does not reflect SPC timeline which concerns long term strategy and planning
SPC is targeting the Sept. 26 F2F with Governing Board meeting for the first strategy proposal
2020 LFN budget planning will be in October and based upon the strategy worked out by GB with SPC input2022020 LFN budget planning will be in October and based upon the strategy worked out by GB with SPC input0 LFN budget planning will be in October and based upon the strategy worked out by GB with SPC input
Iruya planning
To help understand the scope of Iruya, request PTLs edit Iruya Proposed Functionality to indicate their intended release content of Iruya.
Still determining structure of the release, usual milestones will be used once TSC makes decision.
Concern that further delays will put OPNFV two releases behind upstream
Focus is to pull in Iruya
Preliminary inputs due by: 2019-08-26
Seeking proposal from Release Mgr in next weeks TSC meeting David McBride
Unknown User (bh526r) suggested an informational polling to PTLs and see if they are interested in participating in Iruya release before the end of the year, and if they are interested, what is the intended scope of this release, e.g. new features, maintenance, technical debt etc.
David McBride to prepare SurveyMonkey poll to get PTL input on their participation and scope of Iruya release by the end of this year.
Frank Brockners says that the term "project" should be better defined in the questionnaire (i.e., does project mean "OPNFV" for example, or a sub-project like "Dovetail"
Frank Brockners says that there should be a question about the degree of involvement that projects want from SPC.
David McBride asks about deadline for feedback. Kenny Paul says that no deadline has been set so far; however, the SPC would like the feedback to be complete by the time that the SPC meets with the OPNFV TSC.
Trevor Cooper to post questionnaire to mailing list for discussion.
PM update
Unknown User (jmorgan1) suggests that Arpit attend the TSC meeting to provide update, or Arpit can meet separately with TSC members.
David McBride to follow up with Arpit regarding a briefing to the TSC about PM status.
Infra evolution
Frank Brockners says there are two important considerations: 1) builds, which seem to be a good candidate for offloading to the cloud; 2) how do we use field labs. Deployment and test is not easily offloaded to the cloud.
Cedric Ollivier says that Functest requires jobs on baremetal servers.
Frank Brockners is in favor of a small release at the end of the year to maintain cadence and to provide active projects an opportunity to share and promote their work.
Unknown User (bh526r) and Trevor Cooper suggest a standing agenda item in the TSC to update on SPC activity, although there may not have updates every week.
David McBride comments on bullet showing Iruya release in Q$ '19 and notes that release may not occur until Q1 '20
David McBride asks about marketing/messaging about not having a release later this year. Brandon Wick says that this would be a good topic for MWG. Wants to involve Heather and Jill in discussion.
Frank Brocknerssays that we should discuss Iruya release at the next TSC meeting.
Community elections
David McBride says that nominations close today at 5 p.m. Pacific.
We have about 17 nominations currently
Survey (see link in agenda)
David McBride says that the survey closes tomorrow (July 10).
Jonathan said yes, presumably. But he didn't see the list of names yet, because Heather is working on the list of invitees.
Jonathan says that CNTT would like to get feedback at the F2F.
Unknown User (bh526r) suggested that all TSC members should be invited to participate in the discussion. It is up to each individual whether or not they can make it.
Between now and end of September, we prepare infrastructure and technologies, such as transition to CircleCI
Projects currently relying on Apex or other legacy installers are free to move forward with XCI or other solutions as they see fit
Individual project can choose which way to go, CircleCI or traditional OPNFV CI (Jenkins based)
Each project decides which way to go
Unknown User (jmorgan1) points out that XCI is part of community how as a subproject to releng. Outcome of proposal to make XCI a regular project should not influence whether projects use XCI, or not.
June 11, 2019
Note: TSC members that are available will be meeting F2F at the LFN DDF+Plugfest, in addition to using the usual zoom bridge. The day and time remain the same.
Vote: "Does TSC approve changing the size of the TSC to XX? (+1, 0, -1)"
Community awards update
Extend the nomination period
Reduce award count
Reduce from 3 to 2: Code development, community leadership, testing, integegration
Reduce from 2 to 1: Interns
Vote: "Does TSC approve of reducing the number of awards for each category as described, and extending the nomination period for awards to June 18? (+1, 0, -1)"
Jason Hunt is now TAC chair. He will be helping to define the role.
Community election status
Active user data has been published, per the TSC approved election schedule.
Active user count is approximately half of what it was one year ago.
TSC Nominations scheduled to begin Friday
Self nominations are ok, exceptions need proposal by another person in the community
Review of proposed changes to election procedure
TSC-6 Georg suggests that the procedure should document that the TSC will meet to decide the length of the delay
TSC wants to delay the schedule until the changes to the procedure are decided
The TSC agrees to move the election schedule out one week, beginning with the nomination process. The new date to begin the nomination process is June 21.
David McBride will send mail to the TSC with a link to the proposed election procedure changes, for consideration at the next TSC meeting.
Discussion about reducing the size of the TSC.
David McBride says that the active user list is half of what it was one year ago. This seems to suggest that the TSC could be smaller. Push-back on this assertion from several members.
The TSC agrees to leave the size of the TSC the same for now.
Community awards
David McBride says that nomination period ended June 7 without sufficient number of nominees
Should we reduce the number of awards.
TSC agrees that the number of awards should stay the same for now, but be reconsidered for the next round of awards.
The TSC agrees to extend the nomination deadline to June 21.
David McBride to send mail alerting the community to the new nomination deadline.
David McBride to send email thanking interns for their work during the Hunter release as a means to encourage nomination of interns.
AoB
Unknown User (jmorgan1) asks about status of notifying Phil that Jack / Frank would like to discuss PM status. David McBride says that Phil was notified last week but is currently busy due to having just returned from vacation.
Agree: The TSC agrees to align the SPC rep term with the annual community elections, excepting the initial term, which will begin immediately and extend through the next TSC term (~14 months total).
Update on CNTT meeting in Barcelona in May (Jonathan/CNTT team)
David McBride says that we did not discuss the term for the SPC representative during our previous discussion.
David McBride recommends that the initial representative, Trevor Cooper , serve through the end of the current TSC term and the following term, assuming that he is re-elected to the TSC. Thereafter, a new representative would be elected following the annual community elections.
The TSC agreed to align the SPC rep term with the annual community elections, excepting the initial term, which will begin immediately and extend through the next TSC term (~14 months total).
CNTT Update
Jonathan shares presentation with TSC (see agenda).
Frank Brockners asks about availability of CNTT Reference Model document.
Ravi says that the document will be available later in the summer.
Ravi reviews the table of contents for the Reference Model document (slide 3)
Jonathan presents a rough schedule of activities for the next year (slide 4)
Jonathan says that the intention is to include as many stakeholders as possible. Ravi points out that the event may be limited by physical space.
Frank Brockners notes some similarities to the OPNFV Genesis project and understands the challenge of the task that CNTT is attempting.
David McBride notes that the other proposal, mentioned in last week's meeting, is not on the timeline. Mark S. says that that proposal is unrelated to the project proposal that is expected to come out of the f2f in July.
David McBride notes that OPNFV does not have governance that supports the "umbrella" project described in the timeline in the presentation. Perhaps this could be a work group, instead? Otherwise, the TSC may need to devise some supporting governance.
David McBride suggests adding another milestone, prior to the last milestone in the timeline, for a plugfest event to work on the CNTT reference platform implementation(s) that come out of the Iruya release.
TSC F2F at the LFN DDF+Plugfest on June 11, 3 p.m. (UTC+2), Room M3
David McBride says that TSC members attending the LFN DDF+Plugfest will meet f2f, in addition to the usual Zoom bridge. The time will remain the same.
Unknown User (jmorgan1) says that if the Infra WG has topics, such as an infra transition, then the meetings could be restarted
Unknown User (bh526r) will lead the transition, initially, then hand off to another TSC member. Bin will determine whether to have discussions with the Infra WG.
David McBride points out that this plan might also be an opportunity to plan how to use the infra evolution funds that the TSC put into this year's budget, for which there is currently no plan.
The TSC agrees with the recommendation from the TAC infra WG and will investigate how best to implement the recommendation within OPNFV.
Release update
David McBride proposes the following changes to the Hunter release schedule:
Move Hunter 8.1 to June 28 to avoid overlap with LFN DDF+Plugfest, June 11-14
Cancel Hunter 8.2 - likely conflicts with mid-summer vacation. Also, no compelling reason for this release.
The TSC approves the proposal to change the date for Hunter 8.1 to June 28 and to cancel Hunter 8.2
Release process discussion in the weekly tech discuss meeting. Resumes next Monday.
When will CNTT proposal for new project in OPNFV be available?
Jonathan (CNTT) confirms that CNTT plans to have a proposal for a new OPNFV project following f2f meeting in the second half of July.
Jonathan (CNTT) asks what information does the TSC need.
David McBride says that a schedule for releasing profile definitions would be helpful.
Frank Brockners asked if CNTT would have project proposal that late in August.
Unknown User (bh526r) clarified that what Jonathan says is a big project proposal that covers everything, like Genesis project of OPNFV in the past that is umbrella of some other projects
Unknown User (bh526r) said that new project proposal will be shared in a couple of weeks
Jonathan (CNTT) confirmed that is correct
Unknown User (jmorgan1) asked if new project proposal will go through weekly technical discussion etc.
Unknown User (bh526r) confirmed that everything will go through normal process of OPNFV
PM tasks
TSC previously approved Jira tickets of PM roles and priorities
Unknown User (bh526r) shares slide deck regarding SPC (see attachment to message linked above)
Frank Brockners and Unknown User (jmorgan1) suggest that OPNFV representative to SPC should be someone other than TAC rep, due to significant time commitment
Heather says that proposal may come out of f2f workshop in July
Unknown User (bh526r)Bin says that there will be one or more technical proposals that prepare the technology, e.g. YAML, for implementing CNTT/GSMA specs soon, prior to the F2F workshop in July
Bin is at the OpenStack Summit in Denver. Happy to meet with any OPNFV members who are also attending.
LFN DDF and Plugfest
New name that recognizes wider involvement across LFN.
Location and date
June 11 - 14
Kista Convention Center (Kistamässan), Stockholm, Sweden
Encourage remote connections vs. onsite hardware.
We have a limited number of suitable sites and requiring hosts to support onsite hardware reduces the number of available locations and the effort of the host.
We will still set aside a separate room for plugfest participants.
Projects may still bring hardware to plugfests if they wish, but they must make their own arrangements with the host and support is not guaranteed.
Winter plugfest
ONAP would like to move the next LFN DDF and Plugfest after the June event to Feb/Mar 2020 due to a change in release cadence.
License scans
Projects will be contacted by Steve Winslow regarding license scan issues.
TSC focus areas/tasks (incl. PM Task Review) Frank Brockners
Note: it seemed that Cedric Ollivierhad an issue with the minutes, due to an email that he sent prior to the meeting; however, he later clarified that his issue was not the minutes, themselves, but a topic referred to in the minutes.
Chair report
Bin is at OS Summit this week and invites members to connect with him if they're available.
LFN DDF and Plugfest
David McBride says that LFN is encouraging attendees to use remote connections, rather than bringing hardware to the site, as in the past.
LFN will no longer vet host sites based on their ability to support hardware.
Plugfest participants will be provided with a dedicated room
Attendees may still bring hardware if they wish, but they must make arrangements directly with the site host and there is no guarantee that the hardware will be supported.
Kenny Paul says that the reg page should be available today.
The winter event may be pushed out to Feb/March 2020, instead of Dec/Jan, as usual. The TSC will need to decide whether to participate.
Frank Brockners asks whether OPNFV could align its release cadence with ONAP, in order to have a release available for a Feb/Mar plugfest. David McBridesays that it's possible.
Unknown User (jmorgan1) asks whether we have a location lined up for the next event. Kenny says that there is ongoing activity to find a location, but no location has been identified, yet.
Unknown User (bh526r) will send message to TAC and ask TAC's Board Representative regarding:
the decision process of having a LFN PlugFest, i.e. whether or not it needs each TSC's approval according to Governance model
Individual Project's needs to have its own PlugFest that is critical to achieve its strategic priority
David McBride informs the TSC that Steve Winslow is taking over the process of contacting projects regarding license scan issues, so project leads should be sure to review his emails, either directly, or to the opnfv-leads mailing list.
No comments, minutes approved for the past two meetings.
CNTT/GSMA Representative:
Rabi (Vodafone),
Vincent (Orange) and
Jonathan (AT&T)
Rabi introduced himself and Jonathan and started to present
Rabi started with Problem Statement
Rabi indicated that GSMA is defining a standard
i.e. NFVi abstraction and profiling
Frank Brockners asked "Is there an example available that shows how a SW profile looks like?"
Rabi gave an example, e.g. service chaining with NSH
Rabi said it is human-readable configuration
Rabi also introduced Roadmap of defining this standard, e.g. getting input from CNTT to GSMA PRD, and also feedback from OPNFV
Then Rabi described the GAP of consuming the standard of Common NFVi
i.e. No place in industry of implementing the reference implementation of common NFVi models, and profiles are needed
Vincent added that this is ongoing work
Jonathan continued introduction of VNF Certification Lifecycle, in particular about Verification on NFVi without MANO
Jonathan explained CNTT group (Common NFVi Telco Task Force)
Jonathan says that program is MANO agnostic
Trevor Cooper asked how Task Force is a formal group, i.e. how does it operate
Mark Cottrell answered that Task Force intends to be short-lived. It stands up with common standards with GSMA, continues improvement with work of GSMA and OPNFV, give updates to OPNFV, e.g. OVP ecosystem. Ultimately, Task Force will become operational within OPNFV
Trevor said then feedback will go away
Mark C clarified that TF may become part of OPNFV. Feedback will still be there
Rabi added that TF intends to accelerate industry work
Jonathan clarified that it would be an OPNFV project, however collaboration can work out
The real key is the sponsorship
Mark C added that the real key, as Rabi indicated, is to accelerate the industry
Jonathan added that we become OPNFV can become the Gold Standard of common NFVi, that is the ultimate goal
Rabi said that OVP has huge potential. In order to make it successful, we believe that we need right tooling. By having OPNFV to look into the RI of NFVi, it will help OVP.
Unknown User (jmorgan1) suggested we may need deep technical discussion in Weekly Technical Discussion
David McBride asked how to start new project? what is the plan? Will CNTT write a proposal? Staffing?
Mark C clarified that we may need more discussion on that, e.g. resources.
CNTT will meet in Barcelona to work out more details.
The reality is that we cannot do it all by ourselves, and we need support from community and LFN
The combination of both operators (e.g. Vodafone, Orange, AT&T) and OPNFV community resources
Rabi added that e.g. FuncTest project, plus performance testing etc.
A combination of what OPNFV is working on today (testing), plus a new structure if needed
David McBride suggested that CNTT puts together a proposal of new project for TSC approval
Unknown User (jmorgan1) added that his suggestion is to help CNTT by detailed discussion in weekly technical discussion, and help CNTT to work out and polish a new project proposal for TSC approval
Unknown User (bh526r) summarized that based on discussion and suggestion, the path include:
CNTT continues to work out first draft of common NFVi model
OPNFV and CNTT collaborate for detailed technical discussion in weekly technical meeting
OPNFV and CNTT collaborate to work out new project proposal for TSC approval Common NFVi Update
Unknown User (jmorgan1) says that this discussion would be better in the weekly tech discussion meeting
Trevor Cooper points out that this initiative has strategic implications and is therefore appropriate for the TSC
David McBride suggests continuing a high level discussion in the TSC, but reserving technical details for the tech discuss meeting. Will confer with Bin to determine a solution.
Due to a lack of quorum, approval of minutes is deferred until next week.
Chair report
Unknown User (bh526r) reminds the TSC of the developer gathering at Intel today, 9 - 5, followed by dinner onsite.
Focus area / tasks for LF PM / RM
TSC-19 - Frank Brockners suggests developing and presenting a release process proposal to the TSC for discussion
David McBride points out that community involvement has been lacking.
Unknown User (jmorgan1) says that the release process should not necessarily be driving by LF. Better to be driven by the community.
Unknown User (jmorgan1) suggests presenting proposal to the weekly community tech discuss meeting, gaining consensus, followed by presentation to the TSC.
Unknown User (bh526r) suggests syncing on Friday to decide on timing for presentation
Multiple JIRA issues task the PM to setup meetups at various events (ONS, Kubecon, etc.).
David McBride points out that there is no budget to support those meetups.
Frank Brockners says that if the meetup is hosted by a community member organization, with no registration or other administration, and attendees pay for their own meals, then there should be no cost, other than the effort of the PM.
David McBride to confer with Phil and get back to the TSC.
David McBride to identify PM tasks in JIRA that have not yet been identified
David McBride asks TSC members to review proposed updates to TSC procedures document, regarding guidelines for proxies, that are documented in TSC-18, which will be discussed and voted on at a future TSC meeting.
Qiao Fu asks about the duration of the internship (4 - 6 months possible?)
David McBride to check with Min and respond to Qiao Fu with an answer
Promise project termination proposal
The TSC approves the proposal to terminate the Promise project.
PM task documentation and prioritization
Frank Brockners suggests using JIRA to document tasks, followed by a review and prioritization by the full TSC. Wants to avoid a separate working group.
Frank Brockners proposes that community members add tasks to JIRA then review next week
David McBride to send email to community soliciting JIRA issues to document PM and RM tasks
it seems that there was a misunderstanding of Manuel's opinion. Unknown User (mbuil) is satisfied with the response that he received. Unknown User (bh526r) will send an email to the TSC explaining the situation and requesting additional input.
Mar 19, 2019
Agenda
Approval of previous meeting minutes (Feb 26, Mar 5, and Mar 12)
Feb 26 minutes were not posted when minutes were approved at Mar 5 meeting.
March 5 minutes were not approved due to lack of quorum at March 12 meeting.
Vote text: "Does the TSC approve of reducing the current TSC term by approximately 2 months in order to avoid overlapping with budget discussions? (+1, 0, -1)"
Vote text: "Does the TSC approve of the proposed schedule for community elections (+1, 0, -1)"
Phil asks for a list of high priority tasks for PM and RM in OPNFV
Phil says that more tasks should be taken on by the community
Frank Brockners OPNFV does not have a PM since Jun/23/2018, which is the day when Ray Paik left LF.
Frank Brockners By the end of 2018, ONAP was in need of a release manager, after a community member stopped serving as release manager.
Frank Brockners As part of the budget process with the LFN board, OPNFV has an allocation for 1 PM and 0.5 release manager. Per the board decision to reduce expenses, the LFN board decided to share the release manager between OPNFV and ONAP.
Frank Brockners Given that the ONAP community could not find a new release manager within the community, Phil Robb decided to dedicate Jim Baker to ONAP as release manager. Jim Baker started in January 2019 and is serving ONAP as a release manager as well as the OVP program since then.
Unknown User (mbuil) raises the concern if perhaps OPX is difficult to integrate in OPNFV because it requires specific hardware or if maybe there is a full-software version that we could eventually use(mbuil, 13:43:53)
The TSC approves of an ad hoc election to fill the vacant seat.
David McBride says that nominations will begin today. Will send an email to the mailing list.
Community election schedule
David McBride explains that the proposed schedule pulls the election schedule in by about 2 months in response to the TSC saying last year that the election process should not overlap with the budget process. Since the term of 12 months is specified in the election process, the TSC needs to also vote to reduce the current term by 2 months.
The TSC approves reducing the current TSC term by approximately 2 months in order to avoid overlapping with budget discussions.
The TSC approves of the proposed schedule for community elections.
Release update
MS6 - Mar 15. Good response, but still following up with a few projects. See Hunter release page for details on compliance.
MS7 - stable branch - March 29
Mar 12, 2019
Agenda
Approval of previous meeting minutes (Feb 26, Mar 5)
Note: Feb 26 minutes were not posted when minutes were approved at Mar 5 meeting.
Unknown User (mbuil) asks about LFN CoC. Heather says that it does not currently exist, but could be put in place if the community would like to do that.
OPNFV installer status and OVP
David McBride shares slide deck that describes installer status and suggests XCI as a possible solution.
Cedric Ollivier mentions functest also doesn't rely on an opnfv installer and has acheived gating solution
Mark Beierl suggests that LFN and opnfv define what an opnfv platform is without an opnfv installer
Fatih Degirmenci talks to current status of XCI and mentions it supports baremetal since fall last year
Need to clarify project status of XCI. Unknown User (jmorgan1) says that a similar situation exists for LaaS.
Mark Beierl asks if XCI needs to be its own project, instead of a sub-project of releng as it is now.
XCI needs to have more visibility in the wiki. When going to wiki.opnfv.org, the projects page is the first seen. XCI does not get mentioned under any of the Projects lists.
LF will contribute one reviewer (probably Phil or Heather)
mbeierl suggests asking for more volunteers as part of the email soliciting additional intern project proposals
Committer removal process update
The TSC approves the changes to the committer removal process.
Code and release quality improvements
Cristina Pauna provides a recap of what we've covered on this topic, so far, and what decisions have been made.
TSC has agreed to two proposals, so far:
Removal of inactive committers
Code review best practices wiki.
Cristina Pauna asks, should projects be required to run Functest as a prerequisite to merging a patch?
Process is currently in place, question is whether it should be a requirement.
Cristina Pauna will propose a document in which the requirement should be documented
Cristina Pauna will poll installer owners about the requirement
Test tool visibility
Unknown User (mbuil) says that we need a way to easily package and deploy test tools. This is also something that Heather Kirkseyhas encouraged for some time.
LFN infra meeting on Fridays. Trevor Bramwell attending on behalf of OPNFV.
TAC chair election. LF to draft job description.
Document review to be done on GitHub from now on.
TAC meeting scheduled for next week (Feb 27) at 7 a.m. Pacific.
Termination reviews
NetReady
Georg Kunz says that the project has been inactive lately and has completed its primary goals.
The TSC approves the proposal to terminate the NetReady project.
Pinpoint
No one available from the project.
David McBride says that the project has been dormant for years.
The TSC approves the proposal to terminate the Pinpoint project.
Intern project proposal process
David McBride describes proposal, which has been updated since last week per feedback received.
The TSC approves the intern project proposal process.
Note: the 'endvote' command was not entered, so meetbot did not tally the results of the vote and publish them in the HTML log as usual. However, you may see the individual votes in the text log.
David McBride to prepare schedule for TSC review per the approved inter project proposal process
Please add Un-conference proposals to the wiki page
Any ONS attendance (unconference, demo) requires purchase of an ONS pass.
OCP
Continuing collaboration with OCP. LFN will have a booth at the OCP Summit, Mar 14-15, San Jose, CA.
David McBride to coordinate with Kenny Paul on soliciiting feedback on the possibility of bringing Edge gear to plugfest/DDF
Plugfest/DDF report in review
Intern program update
Frank Brockners suggests producing a ranked list instead of a recommended list
Do we need more flexibility? Should we spread out the intern selection throughout the year?
Frank Brockners suggests selecting one intern beginning in March, then two in the summer.
Mark Beierl proposal: align internships with releases: 2 for fall release, 1 for spring?
David McBride to update process proposal per feedback.
Termination review update
The TSC approves the proposed update to the project termination process.
Release update
Hunter MS5 scheduled for March 1.
David McBride asks scenario owners to make sure that their scenarios are documented on the scenario status page and to verify that their scenarios are running in OPNFV CI and passing deployment and health check.
David McBride to close TSC-13 once the termination proposal process has been updated, per today's vote.
David McBride to create JIRA issue for intern project proposal process
Trevor Bramwell suggests adding an issue to document PTL election guidelines. Trevor will create the JIRA issue. Goal is to document guidelines while maintaining OPNFV tradition of giving projects broad latitude in how they select their PTL.
Discussion about history of PTL selection in OPNFV.
Frank Brockners says that OPNFV has always emphasized project autonomy and independence in PTL selection. This may explain why no process is documented.
Scan the projects of inactive committers and confirm with the PTLs that they can be removed, then proceed with the removal procedure
Improve gerrit best practices
Enforce the practices that can be done via Jenkins (e.g., prohibit merging own patches)
Use Functest to verify installer patches
By running a subset of the Functest tests for all patches made on installers before they are merged we make sure basic functionality is not broken by patches
Implemented, but recommend adapting as formal policy
Expand to feature projects
Document the procedure to disable the verify jobs: an approval from the Release manager or TSC should be required
Reduce the time it takes for running the tests
Parallel testing (run in parallel tests from the same tier or run tiers in parallel)
Cristina Pauna says that ODL has a gerrit best practices page
We will continue discussion about gerrit best practices in the weekly technical discussion. Specifically, should we enforce, or simply recommend against self-merges?
IT/Infra
Trevor Bramwell to send IT/Infra update to the TSC mailing list.
David McBride found that the charter already says that the TAC representative may be the TSC chair, or any other member of the TSC, as designated by the TSC. So, no additional documentation of the TAC representative is necessary.
The TSC approves of the proposal that the TSC Chair will be the TAC representative
Intern discussion
David McBride says that we are limited to 3 interns this year, therefore, we will need to be more selective about which intern proposals get selected.
We will implement a plan to solicit, review, and select proposals. Details will be presented to the TSC in the coming weeks.
Release update
Gambia 7.2 went live on Monday, Jan 28
Still reviewing status of Hunter MS3.1. Unknown User (trozet)reports that Apex is currently meeting those requirements.
IT/Infra update
Jenkins upgrade on Weds, Jan 30
Gerrit migration and system reboots to be scheduled for Feb 13th
Community election procedure
Note: Last week,Cedric Ollivier requested more time to review the proposed change before today's vote, but then was unable to attend the meeting. However, David McBride had an email exchange with Cedric before the meeting, who indicated that he had reviewed the change and would have voted to approve it, had he attended the meeting.
The TSC approves the change to the community election procedure as described in TSC-4.
Action item review
Reviewed one new action item:
Closed three action items: TSC-2, TSC-4, and TSC-8.