Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

RepresentativeOrganizationRole

Deutsche Telekom AG

TSC Chair, Active MaintainerX

Deutsche Telekom AG

Active MaintainerX

Ericsson

Active MaintainerX

KDDI

Active MaintainerX

Orange

TSC Deputy Chair, Active MaintainerX

Radisys

EUC Representative

Summit Tech

EUC Representative

Telefonica

Active MaintainerX

Telefónica

Active MaintainerX

Verizon

EUC Representative

Vodafone

TSC Deputy ChairX

Vodafone

Active MaintainerX

Vonage

Active Maintainer
George Glass

TM Forum

TM Forum RepresentativeX

TM Forum

TM Forum Representative

GSMA

GSMA RepresentativeX

GSMA

GSMA RepresentativeX

LF Staff:

Community: Ming Hui Foo Pierre Close Tanja de Groot Laszlo Suto Uwe Rauschenbach 

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.

...

Action Item Review

Governance & Project Management issues

  • CAMARA Board Meeting on April 25th - short debrief (Herbert Damker )
    • No questions or feedback about API backlog, Commonalities, Identity & Consent Management
    • Release Management - Herbert mentioned need for additional Community Release Manager(s)
    • API Sub Project Lifecycle - shortly introduced issues #122 and #129 - the Board general expressed support for the lifecycle stages 
    • EasyCLA vs Developer Certificate of Origin (DCO) - options presented and discussed, Board asked for time until next meeting
      • In consequence EasyCLA deactivated also on QualityOnDemand repository (was activated for test purposes)
      • Tendance is to go to DCO but not yet formal decision. Mark Cornall  from GSMA recommends DCO has we know how it works already in several projets. 
        • DCO is not usual as several open source projets moved to this.
  • New way to manage Maintainers of Sub project in teams and as members of github.com/camaraproject
    • Aim is to improve the management of access rights regarding effort and reliability
    • Proposed way, tested for QualityOnDemand  
      • Maintainers of all Sub Projects will be invited as members to the CAMARA GitHub organization
      • For each Sub Project there will be a GitHub team
        • can be mentioned in GitHub as @camaraproject/<respository-name>_maintainers
        • can be added as reviewers to PRs within the Sub Project
        • will have "triage" access within the Sub Project (only code owners have "write" access)
      • The parent of all these teams is @camaraproject/maintainers
      • Further changes to support the above:
        • The CAMARA admin team will get owner of all MAINTAINERS.md and CODEOWNERS files
        • A change of these will be approved and merged if the majority of the existing Maintainers in a Sub Project have approved the change request (exceptions for new Sub Projects)
        • The MAINTAINERS.md files will get a new column "GitHub Name"
    • Discussion 
      • ...

...