Meeting 31.03.2025

Attendees

  • Markus
  • Stefanie
  • Richard
  • Maiia
  • Andrei
  • Christoph Schreiner
  • Christoph Kraus (Chris)
  • Ben
  • Philip

Not here:

  • Johannes

Cannot come:

  • Moritz (not approved)

Buddies

  • Ben & Philip
  • Moritz & Richard
  • Andrei & Maiia
  • Stefanie & Christoph
  • Filip & Johannes & Richard (Infrastructure)
  • Lukas & Jannis (Project)

Agenda

  • 09:00 start
  • Meeting Notes: Maiia
  • Heartly welcome: Ben, Philip and Christoph Kraus (Chris)
  • Terms
  • update on weekly iterations
    • two approvals before requesting my review
    • don't merge yourself
  • how to find your research question (RQs)
    • a too planned RQ is often boring
    • instead simply work on the issues for a month or so and be open where there are interesting results
    • Stef experience
    • keep it narrow enough, so that it has some depth
    • e.g. continuous releases okay for working title but should be refined
  • current focus 0.5.0 release:
    • migrations
    • CI
    • one last big MR
    • team
    • small bug fixes
  • steps for finding RQs in a month or so:
    1. work on several issues for some time
    2. use some tools, e.g. to benchmark
    3. do some literature research about what others do
    4. brain storming of several RQs or hypothesis
    5. reiterate and refine
  • give approach a name
  • infrastructure "emergency dienst":
    • Johannes: Montag, Freitag
    • Filip: Mittwoch
    • Richard: Dienstag, Donnerstag
  • infrastructure "Wartungsfenster" fixe Zeiten wann upgrades durchführen wo (etwas brechen könnte):
    • Freitag früh 08:00-10:00
  • break
  • Tasks for Everyone
  • Development Board

Tasks for Everyone

To be done until Thursday 03.04.2025 23:59:

  • buddy talk: welcome&onboarding
  • review requested MRs, including meeting MR
  • complete your issues or state in the issue any block/alternative
  • create/update issues for yourself

Do as needed:

  • request reviews
  • submit a page of text in submissions
  • get MRs done

Meeting Notes

  • 09:00 start
  • Meeting Notes: Maiia
    • Copy agenda to bottom (Meeting Notes)
    • Everyone: Approve meeting notes PR once requested for approvals
  • Heartly welcome: Ben, Philip and Christoph Kraus (Chris) (Christoph Kraus (Chris) needs first confirmation from employee, so it is not yet fixed.)
    • Ice breaker (preferences in sweets, technologies)
    • Markus - initiative's founder, here from the start
    • Christoph S., Andrei - also here for a long time
  • Terms in scientific text:
    • establish them clearly
    • refer to our glossary
    • FLOSS vs. OSS vs. Free Software
      • May use same license
      • OSS: "we want best software, open source is best way to achieve it"
      • Free Software: "it is morally right to write and use free software"
      • FLOSS: the former two put together, abstracts away from ideology & politics
    • Initiative vs. Project
      • initiative: people working together with a goal
      • project: also working together with goal but with a deadline (project end)
    • Thesis:
      • repeating terms (nouns) is not an issue and might even be necessary - it is important to use exact terms in scientific papers
      • careful usage of scientific terms (e.g. statistical significance) - only if they are meant that way
  • GitLab Issues:
    • for help about GitLab you can ask Andrei
    • triage: "technical analysis", e.g. finding out what is the root cause of problem, not yet implementation itself
    • in progress: when you start working on an issue, add "status:: in progress" label
    • in review: when you have finished all requirements to close an issue, add "status:: in review" label and assign reviewers
    • each week do some progress on your issues
  • MR (Merge Requests):
    • Use MR template
    • Review 3 times more MRs than you author
    • Two approvals before requesting Markus' review
    • Don't merge yourself (Markus is usually responsible for merge)
  • how to find your research question (RQs)
    • a too planned RQ is often boring
    • instead simply work on the issues for a month or so and be open where there are interesting results
    • Stef experience: Stef explored different image optimizations approaches and then picked the most promising one to go deeper into it and write about
    • keep it narrow enough, so that it has some depth
    • e.g. continuous releases okay for working title but should be refined
  • steps for finding RQs in a month or so:
    1. work on several issues for some time
    2. use some tools, e.g. to benchmark
    3. do some literature research about what others do
    4. brain storming of several RQs or hypothesis
    5. reiterate and refine
  • give approach a name
  • have a "working title" (e.g. optimizations, continuos releases)
  • name your technical approach (e.g. you improve performance with Lazy Loading and name it "VeryLazyLoading")
  • specific name makes it easier to refer to your contribution and write about it
  • infrastructure "emergency dienst":
    • Johannes: Montag, Freitag
    • Filip: Mittwoch
    • Richard: Dienstag, Donnerstag
  • infrastructure "Wartungsfenster" fixe Zeiten wann upgrades durchführen wo (etwas brechen könnte):
    • Freitag früh 8:00-10:00
  • current focus 0.5.0 release:
    • migrations
    • CI
    • one last big MR
    • team
    • small bug fixes
  • Break 9:55-10:05
  • Team's Tech Env:
    • VS Code: Andrei, Maiia, Richard, Cristoph S.
    • WebStorm: Stefanie
    • Linux: Richard
    • Windows: Andrei, Maiia (wsl), Cristoph S., Stefanie (wsl)
    • MacOs: Cristoph S.
  • Tasks for Everyone
  • deadline: Thursday midnight
  • buddy talk: welcome & onboarding
  • review requested MRs, including meeting MR
  • complete your issues or state in the issue any block/alternative
  • create/update issues for yourself
  • Development Board