Technical Lead Circle [2024-12-16]

[antonkri]

Agenda

1. Approval of meeting minutes
2. Review call for PRs:

• Project planning overview #58

3. Renaming to S-CORE
4. Setting-up of working groups and communities
5. Nomination of community leads
6. Creation of Teams and CODEOWNER files
7. Overall Roadmap & create structure for planning
8. Additional meeting CW51?

Meeting Minutes

1. Approval of meeting minutes
   • Meeting Minutes approved
2. Review call for PRs:
   • Project planning overview #58 to be reviewed until end of this week
3. Renaming to S-CORE
   • Renaming to distinguish e.g. between S-CORE (Safe) / R-CORE (Realtime) / ...
   • Would have impact on ...
     • Project name itself in documentation, marketing, ...
     • Logo
     • Repositories
     • GitHub Organization
     • Domain
   • To be discussed in next Project Lead Circle
4. Setting-up of working groups and communities / 5. Nomination of community leads / 6. Creation of Teams and CODEOWNER files
   • GitHub Teams can only be created by Eclipse Foundation
   • To be clarified whether we can add people to GitHub Teams or if this has to be done via Eclipse Foundation
   • Creation of GitHub Teams for Technical Leads & Communities & Cross-Functional Teams (https://eclipse-score.github.io/score/platform_management_plan/project_management.html#technical-committees) -> @antonkri
     • automotive-score-technical-leads
     • community-operational (Also to be renamed in platform handbook)
     • community-testing
     • community-architecture (Community Lead: @qor-lb)
     • community-process
     • cft-persistency
     • cft-logging
     • cft-communication
     • cft-orchestration
     • cft-feo
   • CODEOWNER file:
     • https://github.com/eclipse-score/inc_feo -> @eclipse-score/cft-feo
     • https://github.com/eclipse-score/inc_mw_com -> @eclipse-score/cft-communication
     • https://github.com/eclipse-score/inc_mw_log -> @eclipse-score/cft-logging
     • https://github.com/eclipse-score/inc_mw_per -> @eclipse-score/cft-persistency
     • https://github.com/eclipse-score/process_description -> @eclipse-score/community-process
     • https://github.com/eclipse-score/bazel_registry -> @eclipse-score/community-operational & @eclipse-score/automotive-score-technical-leads
     • https://github.com/eclipse-score/score -> @eclipse-score/community-architecture
     • https://github.com/eclipse-score/reference_integration -> @eclipse-score/automotive-score-technical-leads
   • Community meetings to be invited via Eclipse Foundation by Community Lead
   • PR to include link to GitHub Teams in https://eclipse-score.github.io/score/platform_management_plan/project_management.html
   • Create discussion for each Community & Cross-Functional Team
   • Nomination of community members in https://github.com/orgs/eclipse-score/discussions/90 -> until January 13, 2025
   • Nomination of cross-functional members in software architecture community
5. & 8. not discussed, further exchange via Slack planned

General:
- PRs shall be at least be approved by two committers before merging -> @ltekieli
- @antonkri to create "List Open Points" as GitHub Project