Meeting 2023-08-08

Tasks for Everyone

To be done until Wednesday 2.8.2023:

To be done until Friday 4.8.2023:

  • Get current use cases (UC) done
  • Write at least one page in submissions
  • Update sprint plan
  • Do at least 8 reviews of PRs in main repo or submissions

Individual Tasks

To be done until Friday 4.8.2023:

  • Paul: read-only, Arbeit schreiben
  • Adi: manual+automatic tests
  • Moritz: heatmap, documentation
  • Thorben: intro tour done, User Study done
  • Lukas: unify PermaplanT setup
  • Gabriel: shade layer, case study+docu+testprotocol for heatmap
  • Christoph: DB docu update, improve scraper, deutsche Namen, hierarchy
  • Samuel: NC hierarchy, (share) base layer
  • Markus: release
  • Yvonne:

Attendees

  • Samuel (Protocol done)
  • Adi
  • Moritz
  • Christoph
  • Markus

Buddies

  • Adi & Samuel (NC fixes)
  • Moritz & Christoph (security/performance testing strategy)

Agenda

PermaplanT

  • 09:00 welcome
  • protocol: Samuel
  • feedback/lessions learned
    • duplicates
    • bureaucracy
  • Gabriel fertig
  • case study
  • projekt neu 194.145 and 194.146
  • Mo vs Di Treffen?
  • code quality within PRs, identified features and usability improvements in follow-up issues
  • always write/update/ask implementation issues before starting working on them
  • update release todos
  • 0.3.1 and 0.3.2 released, see Changelog
  • sprint plan
  • outlook

Outlook: Tasks for Everyone

To be done until Friday 11.8.2023:

  • Get current use cases (UC) done
  • Write at least one page in submissions
  • Update doc/authors.md and avatar in NC nextcloud/Public/Avatars/
  • Write if interested in projects:
    • projekt neu 194.145 and 194.146
    • 185.A28 PR Project in Computer Science 1 4.0h, 6.0EC
    • 185.A29 PR Project in Computer Science 2 4.0h, 6.0EC
  • Update sprint plan
  • Do in total ~80 reviews of PRs in main repo or submissions

Outlook: Individual Tasks

To be done until Friday 11.8.2023:

  • Adi: NC config, finish Makefile, modularization, create/cleanup/prior CI issues
  • Moritz: documentation, seeds, shade, polygon, (base layer)
  • Christoph: plants hierarchy+overrides, security/keycloak roles strategy
  • Samuel: NC hierarchy, (share) base layer, cleanup issues/PRs

Meeting Notes

Feedback: - same/conflicting information at different locations

Project: Look at new PR courses: 194.145 and 194.146 Project is work hour focused

What should be in PR what in follow up issues: - code quality issues or missing documentation in PR - functional extensions can be in follow up issues Guideline: repository should be in a better state after each PR

Write issues with specification before starting to work on it. Update issue description and ask if it is still correct/relevant before starting to work on it.

Hierarchy Implementation Proposal accepted.

Hierarchy extension: Plant icon name in database for different hierarchy levels. Frontend gets the icon name it should request from Nextcloud.