2023-12-21 TSC Minutes

Attendees & Representation

TSC Members may indicate their attendance by marking an X in the column to the right.

Community members may use @name tag to mark their attendance below the table. 

LF Staff: @Casey Cain 

Community:   @Ramesh Shanmugasundaram @Nick Venezia @Tanja De Groot 

Agenda

The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF. Antitrust Policy

Open

• Roll Call

• Action Items Review

• Agenda Bashing

• General Topics
  
  

  • API Backlog

  • Commonalities

  • Identity & Consent Management

  • Release Management

• Any Other Topics

Minutes

Action Item Review

Rule concerning previous meeting minutes approval: If no issue explicitly raised the meeting minutes are considerate as validated.

API Backlog

• Name proposals and initial maintainers for already approved sub projects:

  • Population Density Data - see https://lists.camaraproject.org/g/tsc/message/88

    • Approved

    • OK to proceed with the working group

      • Possibly another maintainer from Orange

  • Short Message Service - see https://lists.camaraproject.org/g/tsc/message/87

    • Approved

    • OK to proceed with the working group

• Proposed agreement (as already practised for some sub project proposals):

  • Decision about names & maintainer lists for already approved sub projects will be taken in lazy consensus if there there are no objections or additional nominations on the TSC mailing list within 48 hours

    • OK - no comment from the group

• Proposed agenda topic by Nick Venizia in https://lists.camaraproject.org/g/tsc/message/90

  • Recommendation: Need to be discussed first in API Backlog to get a first feedback. Normally discussion in TSC cames after this first discussion in API Backlog

Commonalities

• Reports given by Ludovic and Eric

• Important updates:

  • Progress with linting, adaption ongoing by sub projects

  • Work move forward for Test Case as some company provided comment on issue Test definitions - implementations guidelines and artifacts · Issue #94 · camaraproject/Commonalities (github.com)

    • Shilpa offered to create a short Camara-API-Testing-Guidelines.md doc 

• Call for action (mains)

  • Version 0.2.0 of documents and artefacts available. Sub project are asked to state to which release they are compliant.

• Issue about X-Correlator (Set X-Correlator as Required in OAS Definition, X-Version removed by jlurien · Pull Request #115 · camaraproject/Commonalities (github.com)) as we have a consensus.

  • This will not go in release 0.2 but next release

• Shilpa mentioned the CAMARA_common.yaml  PR (Update and rename CAMARA_common.json to CAMARA_common.yaml by shilpa-padgaonkar · Pull Request #107 · camaraproject/Commonalities (github.com)) that define common data types for CAMARA APIS

  • Probable impact on some API

• Eric raised the point about tagging the issue related to input from the End_User council.

  • We need to think about it.

A lot of works has been in Commonalities this year

Identity & Consent Management

• Report given by Diego

• Documentation update with securitySchemes final agreement.
  
  

  • PR: https://github.com/camaraproject/IdentityAndConsentManagement/pull/93. Comment by Eric has been considered as an addition, Client Credentials now appearing as an option

  • Release 0.1.0 to be made available once former point is merged

• Issue about adding further clarification for scenarios where user consent is not given (PR#86 Auth code flow update to fix issue #70 by jpengar · Pull Request #86 · camaraproject/IdentityAndConsentManagement (github.com))

• Issue about securitySchemes final agreement (Documentation update with securitySchemes final agreement by jpengar · Pull Request #93 · camaraproject/IdentityAndConsentManagement (github.com) ) we are on final steps before validation

  • Jan mentioned the issue Claims to be used in oAuth Access tokens/ OIDC Identity tokens · Issue #100 · camaraproject/IdentityAndConsentManagement (github.com)

    • It could be resolved by documentation. This is not a showstopper for the release 0.1 - Then we can solve this one and release 0.2.

• Question about how we can proceed for CAMARA Profile - Do we want to use existing one or build one. 

  • Diego think it's better to craft our own profile (and filling gap from OIDF one) in order to move faster.

  • Shilpa agreed on this and making a combination from FAPI2 assets & new from CAMARA

Release Management

• Important updates:

  • Ludovic & Casey raised the point that we're missing Release Manager and we need 2

    • José highlighted that this role need a lot of dedication and probably not fdar from a full time job so not easy to find someone in the team

    • First: This point must be raised to the board (Herbert will do)

    • Then - alternatively  - Casey mail about looking for volunteer could be also send to the complete member list

      • Training sessions has been recorded

      • If struggling to find links then Casey can help.

• Calls for actions

  • The working group is seeking two volunteers to take on the role of Community Release Manager: https://lists.camaraproject.org/g/release/message/6

  • (Where to distribute the request?)

  • Currently no volunteers

Open Issues in Governance

• #113 Clarity on who are allowed to create new issues in Commonalities and TSC

  • Herbert ok with Jan proposal

  • OK for the team - Herbert will create a PR

• #100 Provide a user-friendly snapshot for CAMARA users and developers

  • Herbert showed the need backlog table proposal

    • Ludovic raised an issue about Device Location 

      • Ludovic/José will craft a PR to solve this.

      • Tanja proposed to align family name with subproject name

      • We can drop this Family concept

      • Tanja also raised that we need also to improve how we find CAMARA assets by some automated scripts.

        • Mark said that Daniel has done some scripting.

• #84 Change Working Groups into Sub Projects

  • "Working Group" or "Sub Project"?

    • They are still "Working Groups", as they are affecting multiple API Sub Projects. Sub Projects is reserved term for API projects

    • Commonalities → Working Group with own repository for their documents and artefacts

    • Release Management → dito

    • Identity & Consent Management → dito

    • Marketing Working Group → Will get "Outreach Committee", no own repository, but material complete in Wiki?

  • Update of project documents to reflect that.

AOB

• Meeting on 1st Thursday within 2024 will be skipped (as agreed within last TSC meeting)

• Next meeting will be on 3rd Thursday, so on January, 18th, 2024  

Action items