Technical Lead Circle [2025-01-13]

[qor-lb]

Participants

• Frank Scholter Peres @FScholPer
• Johannes Glamsch @johannes-esr
• Lars Bauhofer @qor-lb
• Anton Krivoborodov @antonkri
• Rebecca Markert @markert-r

Agenda

1. Approval last meeting minutes
2. Work Mode Cross Functional Teams (CFT)
   • Assumption: Mostly consisting of architectural/development people in Q1
   • Organizer: Feature Request Owner
   • Until Arch F2F in Feb: Breakout for the Feature Request & Current Status OSS Approval for planned contributions
   • After Arch F2F in Feb: Committer for the solution closest to the decided concepts becomes organizer
   • Start after 20th Jan
3. Work Mode Communities
   • Start after 20th of Jan
   • The community should be a place to discuss contributions & solution guardrails
     (not to plan to create them; self motivated contributions! contribute improvements not time)
4. Technical Lead Circle LOP
5. Working Session Tech Lead (2h)
   • Top down planning from milestones across the next year
6. Agenda next Tech Lead

Meeting Minutes

to 1.

• approved

to 2.

• additional land scape analysis for the preparation of features (counts as contribution as well)
• TODO: Explain how communities and CFTs interact with each other (e.g. how are tooling requirements for a specific language allocated to the operational community --> issue boards, labeling, repo, etc.).

to 3.

• TODO: Extend the definition/scope the communities in the project handbook (incl. expected roles) --> @qor-lb
• TODO: Explain how communities and CFTs interact with each other (e.g. how are tooling requirements for a specific language allocated to the operational community --> issue boards, labeling etc.).
  • preparation of repos to track individual issues

to 4.

to 5.

• WS Thursday 16th Jan 10 - 12 CET
• WS Thursday 23rd Jan 10 - 12 CET

to 6.