Meeting 22.07.2024

Attendees

  • Markus
  • Lukas (Protocol done)
  • Christoph
  • Stefanie
  • Filip
  • Andrei

Sick:

  • Yvonne
  • Jannis

Buddies

  • Stefanie & Christoph & Andrei
  • Jannis & Lukas

Agenda

  • 09:00 start
  • presentation Filip
  • protocol: Christoph
  • technical texts:
    • explain step by step (maybe backtracking from goal)
    • clear terminology, don't use words you don't need (e.g. latency, ...)
    • focus on one thing and explain that properly
    • explain data
  • fundamentals of science:
    • method (reproducible or at least clear what was done)
    • results (from method, without opinion)
    • findings
  • standards for scientific texts:
    • related work should compare
    • make "Why?" clear
    • advertise your contributions
    • write about future work
  • improvements of UX (focus group)
  • issue:MR should be 1:1 and always connected
  • Task Board

Tasks for Everyone

To be done until Friday 26.07.2024:

  • last chance, please vote for live meeting
  • create a MR on submissions with a (short) technical text (review next week)
  • approve meeting MR
  • buddy talk: technical text
  • 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 26.07.2024:

  • Stefanie: rework usecases
  • Christoph: hierarchy
  • Lukas: crop rotation
  • Andrei: categorize and improve issues, remembering viewing state

Sick:

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

Meeting Notes

Filip held a presentation about PermaplanT CI explaining the overall architecture and how Jenkins, Docker and Ansible are used.

Thesis

Your thesis should include both a technical text as well as a scientific text.

Technical text

Say one thing as clearly as possible. Every technical person with computer science background should be able to understand it. It might help to backtrack: "What do you have to explain to come to this point?". Then write the minimum amount of text to arrive at your point. First explain the most basic parts and then continue building upon it. You can assume the reader has the general knowledge of someone who studied IT, e.g., you don't have to explain HTML and Javascript but you should explain Konva (if it is relevant). The terminology should be as clear as possible and consistent to the PermaplanT glossary. Always use the same words, don't use synonyms. One trick is to write a technical text and then come back to it weeks later to check if it's still understandable. Alternatively have someone review it.

Scientific text

Explain your method and results, optionally present your findings. Your method should be reproducible. The minimum standard of methodology is that other people understand what you did. For reproducability document your test environment, including version numbers of used software. Findings are the objective result of applying the described method. Other people should be able to come to the same conclusion based on your findings.

For related work do a technical comparison.

Your contributions should only be mentioned in the introduction (not in methodology and results).

It is very important to be consistent with your terminology.