Meeting 24.06.2024

Next meeting 15.07.2024.

Attendees

  • Markus
  • Yvonne
  • Christoph
  • Lukas
  • Andrei
  • Moritz
  • Filip

Not here:

  • Jannis

Cannot come:

  • Daniel

Buddies

  • Daniel & Andrei
  • Moritz & Christoph
  • Jannis & Lukas

After one week, new buddies:

  • Andrei & Christoph
  • Jannis & Lukas

Agenda

  • 09:00 start
  • welcome
  • protocol: Moritz (last protocol)
  • this time: 3 weeks iteration until 15.07.2024
  • next meeting (short check-in) with Yvonne on 01.07.2024
  • last presentation (22.July): Filip
  • version upgrades July (Debian, Rust?, nodejs?)
  • buddy talk?
  • structure of thesis
  • console.log
  • ReinSaat
  • survey: please share, forward
  • SQL constants?
  • push to submissions should work now
  • dev:
    • all MRs to dev branch
    • dev branch migrations
    • reset dev database if migrations are incompatible
  • architecture/split stores?
  • tasks for anyone
  • Task Board
  • Thursday 14:00 heatmap meeting (Lukas until 15:30)

Tasks for Everyone

To be done until Thursday 27.06.2024:

  • approve meeting MR
  • review architecture
  • do reviews, especially for Moritz and Daniel

To be done until Friday 12.07.2024:

  • buddy talk: choose your topic
  • get MRs done
  • request and approve for requested reviews
  • create/update issues for yourself and assign to next iteration

Individual Tasks

To be done until Friday 12.07.2024:

  • Moritz: finished (base layer image offset, finish PRs: group vs. layers, test cases, get UC done)
  • Christoph: hierarchy
  • Lukas: clarification of issues, stat analysis, crop rotation
  • Andrei: categorize and improve issues, remembering viewing state, (maybe afterwards copy&paste)
  • Yvonne: issue about avatars

Was not here:

  • Jannis: offset, go through issues, create issues: (1) tutorial for layer creation (creation/update metadata), (2) what interface should any layer have), (3) unify layer design

Cannot come:

  • Daniel: finished (UC done, tests)

Meeting Notes

This weeks iteration will span 3 weeks. Major upgrades to the infrastructure, specifically to our infrastructure, such as CI Runners are planned. Upgrades to Rust and NodeJS are unclear.

A few notes on the structure of the thesis:

Either do Background OR do related work. Both are usually not necessary, since they both accomplish more or less the same goals in a slightly different manner. Generally, related work should be used for most thesies (Lukas' probably being the only exception).

Cleanly separate Methodology, Results and Interpretation/own opinions.

You may use the official TU-Wien Informatics Thesis-Template, but it is not strictly necessary.

Please don't open merge requests in the thesis-repo for uninteresting changes (e.g. adding the thesis template files). Push those directly to master instead.

Yvonne and Markus met up with the CEO of Reinsaat (the biggest Organic seed Producer in AT) to show the current progress on PermaplanT. They were asked to forward the survey to their customers.

Since we already have all plants from Reinsaat in the DB, the idea is that in the long term PermaplanT users should be able to directly order Reinsaat-seeds from the app.

Reinssat also considered using Permaplant for their internal garden planning tasks.

All PermaplanT members are asked to forward the survery to as many people as possible.

Merge requests should target dev by default. Merging to master should only happen in rare exceptions.