Meeting Minutes

[AlexanderLanin]

All official meetings will be documented in this thread. So if you subscribe here, you'll get summaries of the meetings you missed.

[AlexanderLanin]

Kick-Off

2025-01-28

Agenda

• Welcome new members; What is score?; What is this community?
• Introductions
• Current state & open topics / backlog
• Daily

Important Links

• https://github.com/orgs/eclipse-score/discussions/216

Committers

• Alexander Lanin @AlexanderLanin
• Nikola Radakovic @nradakovic (soon)
• Maximillian Sören Pollak, @MaximilianSoerenPollak (soon)

Contributors

• Dan Calavrezo @dcalavrezo-qorix
• Nicolae Dicu @nicu1989
• Sameer Srivastava @sameer6989
• Aymen Soussi
• Tomas Pereira

Part time contributors

• Daniel Woste @danwos
• Philip Partsch @PhilipPartsch

Stakeholders:

• Rebecca Markert
• Lukasz Tekieli @ltekieli
• VinodReddy GopiReddy
• Sven Bachmann
• Jochen Hoenle, @hoe-jo
• Michal Mueller

Meeting Minutes

• @AlexanderLanin to sync with https://github.com/orgs/eclipse-score/discussions/90
• @AlexanderLanin to clarify whether we can write clear names here!
• Chat: some people have trouble joining slack --> Contact your respective teach lead.
• How to proceed in case of conflicts? --> will be addressed in contributor guidelines by tech leads. For now decisions within the communities can be escalated to comitters, otherwise to tech leads.
• Reminder: everyone needs to sign the eclipse contributor agreement!
• Do we want to structure in sub teams? Let's address this after a few dailies to see how many will actually show up :-)
• how to assign tickets -> for now contact @AlexanderLanin via chat
• how do we get everyone into contributor status? Already in progress by tech leads! Rebecca wiill check again.
• how to assign reviewers -> for now post the PR into chat
• @AlexanderLanin & @ltekieli will look into fixing https://github.com/orgs/eclipse-score/teams/community-operational to reflect reality. Then we might be able to activate CODEOWNERS. @AlexanderLanin to create tickets for that.
• how do we prioritize? -> not answered yet
• how to start working? -> pull a ticket! :-)
• a wiki for already solved problems etc -> we need to be clear what goes into chat, issue, docs-as-code or wiki. @PhilipPartsch and @MaximilianSoerenPollak will discuss their ideas regarding wiki vs docs-as-code.
• A longer meeting will be required in addition to dailies! With an open backlog somewhere.
  • Daily Mo, Wed, Fr 10:30 (on Wednesdays a little longer)

Potential "topics":

• docs-as-code
• guidelines (pyton, rust, c++)
• automations, CI/CD
• OSS / licensing

[AlexanderLanin]

Daily

2025-01-28

Agenda

• Alignment on currently worked upon issues. Specifically identification of dependences and collaboration.

Participants

• Alexander Lanin @AlexanderLanin
• Nikola Radakovic @nradakovic
• Sameer Srivastava @sameer6989
• Maximillian Sören Pollak, @MaximilianSoerenPollak
• Aymen Soussi
• Rebecca Markert

Meeting Minutes

• Contribute to Issues via comment or via pull request. You'll need to fork the repository.
• Operational Backlog
• "Kick-Off": a few more people in our existing community
• Meeting Infrastructure: Meetings stay as they are for now. We'll switch to open eclipse infrastructure mid February: google calender & zoom meetings.
• Chat:
  • Chat-Access
  • Chat
• Let's make issues smaller, so they are estimatable and closed
• Let's create "milestones" what we aim to achieve e.g. end of january / february

OSS deep dive
split OSS (#82, #126) to sub-issues, e.g.:

• setup dash for python on PR (non blocking) -> dash: Integrate DASH tool in Bazel build #155
  • rename "license check" to something like "license dry run"
• automation: print problems as comment to pull request, see also bug: pr-preview comment #211
• create private key for automatic clearance
• extend automaton with automatic clearance
• add rust dependencies to dash (via bazel)
• add C++ dependencies to dash (via bazel)
• bazel modules
• change automation (daily / blocking / etc)

[AlexanderLanin]

Daily

2025-01-29

Agenda / Minutes

• Collect current member status (see below)
• Yet another issue organization attempt: https://github.com/orgs/eclipse-score/projects/6
• Collect what needs to be documented: document current setup #245
• Daily time -> 1 hour earlier? @nradakovic ok?
• Hint: good first issues
• esbonio setup broken? -> @MaximilianSoerenPollak

Participants

• Alexander Lanin @AlexanderLanin
• Nikola Radakovic @nradakovic (soon)
• Maximillian Sören Pollak, @MaximilianSoerenPollak (soon)
• Dan Calavrezo @dcalavrezo-qorix
• Nicolae Dicu @nicu1989
• Sameer Srivastava @sameer6989
• Aymen Soussi
• Tomas Pereira
• Daniel Woste @danwos
• Philip Partsch @PhilipPartsch
• Rebecca Markert
• Lukasz Tekieli @ltekieli
• VinodReddy GopiReddy
• Sven Bachmann
• Jochen Hoenle, @hoe-jo
• Michal Mueller
• Anton

Current member status

who	score-member (GitHub)	chat (Slack)
Alexander Lanin @AlexanderLanin	✔️	✔️
Nikola Radakovic @nradakovic	✔️	✔️
Maximillian Sören Pollak, @MaximilianSoerenPollak	✔️	✔️
Dan Calavrezo @dcalavrezo-qorix	✔️	✔️
Nicolae Dicu @nicu1989	✔️	✔️
Sameer Srivastava @sameer6989	❌	✔️
Aymen Soussi	requested ❓	✔️
Tomas Pereira	❌ (blocked by legal)	❌ (blocked by legal)
Daniel Woste @danwos	✔️	✔️
Philip Partsch @PhilipPartsch	✔️	✔️
Michael Mueller	❌	❌

[AlexanderLanin]

Daily

2025-01-31

Agenda / Minutes

• Attributes we need for GitHub Projects: assignee, estimated start, estimated end, status

• Everyone: What I'm working on. What is blocking me. Where I would appreciate some help.

• Multi-repo setup decision review/feedback requested. PR

• Python-tooling Issue organize vote inside slack python chat + expert meeting

Participants

• Alexander Lanin @AlexanderLanin
• Anton
• Aymen Soussi @Aymen-Soussi-01
• Dan Calavrezo @dcalavrezo-qorix
• Daniel Woste @danwos
• Jochen Hoenle, @hoe-jo
• Lukasz Tekieli @ltekieli
• Maximillian Sören Pollak, @MaximilianSoerenPollak (soon)
• Michal Mueller @mmr1909
• Nicolae Dicu @nicu1989
• Nikola Radakovic @nradakovic (soon)
• Philip Partsch @PhilipPartsch
• Rebecca Markert
• Sameer Srivastava @sameer6989
• Sven Bachmann
• Tomas Pereira
• VinodReddy GopiReddy

[MaximilianSoerenPollak]

Daily

2025-02-03

Agenda / Minutes

• Everyone: What I'm working on. What is blocking me. Where I would appreciate some help.

@MaximilianSoerenPollak will make meeting for python tooling discussion.

PR-Preview issue from forks:
-> Either manual approve PR to build preview
-> Or have a separate repository for the PR's

Branch naming should be restricted to ensure that we do not overwrite 'main' release documentation.

Participants

• Alexander Lanin @AlexanderLanin
• Anton
• Aymen Soussi @Aymen-Soussi-01
• Dan Calavrezo @dcalavrezo-qorix
• Daniel Woste @danwos
• Jochen Hoenle, @hoe-jo
• Lukasz Tekieli @ltekieli
• Maximillian Sören Pollak, @MaximilianSoerenPollak (soon)
• Michal Mueller @mmr1909
• Nicolae Dicu @nicu1989
• Nikola Radakovic @nradakovic (soon)
• Philip Partsch @PhilipPartsch
• Rebecca Markert
• Sameer Srivastava @sameer6989
• Sven Bachmann
• Tomas Pereira
• VinodReddy GopiReddy