2022-02-01 TSC Agenda and Minutes

5 min

@Gergely Csatari

• Quorum met

• Previous Minutes approved

2 min

Announcements

@Beth Cohen

• OpenInfra Summit RFC open is until Feb 9

  • Add session proposals related to Anuket in here: https://cfp.openinfra.dev/app/berlin-2022

  • In Berlin one week before the June development event in Porto

  • Currently planned to in person only

  • There are Forum sessions planned again

  • There will be the usual session recordings

• PTG

  • All virtual

  • Registration is open here: https://openinfra-ptg.eventbrite.com/

  • Agenda is not available yet

• Interim vitual LFN DTF before June around March

  • Initiated as a feedback discussion in the DTF

  • Most probably a 2 days session

  • TAC is interested in the feedback of the communities

  • Proposal: Discuss big cross community questions based on specific topics, like:

    • CNF workload testing

    • Cloud native onboarding

    • Security

    • Cross community documentation discussion

    • Telco/Vendor collaboration on projects and badging support

  • Add a +1 if you are interested in participating: +1

  • Add your name if you are interested in to be in the programming committee: @Beth Cohen @Scot Steele , @Gergely Csatari

  • Feedback from @Cédric Ollivier : having interim events makes the regular meetings more content light and it is difficult to participate in several meetings and releases. There are regular meetings with ONAP about security and documentation.

8 min 

• Slides available here

@Scot Steele

@Beth Cohen

@Brandon Wick will be on call to give update.

• Suggestion to have a monthly marketing update by @Brandon Wick

• Infographic is planned ot be started as a wiki page. Any ideas are welcome to help make Anuket more infographincy

• What is the target of ONEEF

  • 3 days with every day focusing on a specific geographic location

  • All speakers are VP level of higher

  • A collection of best keynotes in 3 days

  • Are these executives are aware of what LFN is doing of they just run a marketing show?

    • Last year there were some interesting conversations. This is really interactive.

10 min

Release Updates

@David McBride

• Requirements for M1 were met.

• CRIV is most probably not participating to Moselle

  • Are there any dependencies on CRIV in other projects?

    • Hearing none

    • If yes please inform @David McBride

• Vote: Does the TSC agree with the recommendation that the requirements of Moselle M1 have been met?

  • Approval of Moselle M1 with 12 yes votes

5 min

@Gergely Csatari

RM - https://github.com/cntt-n/CNTT/pull/2746 - waits for comments or approval from @Walter.kozlowski

RA1 - Done

RA2 - Done

RI1 - https://github.com/cntt-n/CNTT/pull/2777 - waits for review-s

RI2 - Done

RC1 - Done

RC2 - Done

Common, Gov - https://github.com/cntt-n/CNTT/pull/2737 waits for comments or approval from @Pankaj.Goyal and @Walter.kozlowski

2 min

@Scot Steele

@Beth Cohen

No updates

15 min

• Until recently, we had a designated TSC Lead as the master Administrator, in GitHub, that merged any PRs authored by WSLs. This was a decision made at the time CNTT was started.

• A recent PR made a change that would allow WSLs to merge their own changes. I think this is a TSC decision to make.

@Pankaj.Goyal

Will need a vote of the TSC

Discussion about the various roles.  Is the TSC leads the right people to be the master admins?  Way too much overhead and more burden.  

@Cédric Ollivier If we follow the opensource rules, the most important contributors should be as code owners.

@Al Morton I agree with Karine that more than one person should have merger rights. Also, 3 positive reviews should lead to a merger, as the rules seem to state...

To be continued to next week.

• It was discussed over mail that for pr-s affecting more than one sub-project an approval is needed by the lead of all the affected sub-projects.

• We need more than one persons to be able to merge in every case.

• Cooloff time for comments is to short

• After major changes there is a need for re-approvals

• We need 2 codeowners with merging rights for every sub-project, selected by the sub-projects themselves

All of this is described in the CONTRIBUTIONS.md file. @Gergely Csatari to create a pr and invite all TSC members for reivew.

10 min

@Gergely Csatari

Will need a vote of the TSC after review.

• Let's target a vote 2 weeks from now (15. Feb 2022)

15 min

Feb 23, 2021 Minutes

@Trevor Bramwell

Will need a vote of the new TSC.  The previous TSC voted to support this effort.

• Let's defer this to the next meeting and prioritize it.

2 min

Sub-project Leaders

Thoth: Telco's Perspective - AI/ML for NFV : Kindly request those from telco community to fill this survey. This survey is to help Thoth to stay 'relevant' to Telco's needs. Kindly share this link with your colleagues/friends.

Sent the survey to the EUAG mailing list.

5 min

• EUAG:

  • There will be a follow up discussion about Anuket Assured to build interest and be supportive of the Anuket Assured effort

• CVC:

  • Had discussion to have a monthly cadence on project requirement setting and testing requirements

  • Anuket projects are invited to give an update on their status and testing development

1 min

AOB