generated from amosproj/amos202Xss0Y-projname
-
Notifications
You must be signed in to change notification settings - Fork 2
Meetings
Jan Degen edited this page Nov 30, 2022
·
1 revision
A place for meeting documentation.
- Wed, 12:15-13:45: Team Meeting
- Dailies?
Team + Mr. Wieland Eckert
- Robert Balink (SM)
- Dev Darshan Kasthuri Umashankar (PO)
- Saber Jelodari (PO)
- Jens Wächtler (SD)
- Leander Tolksdorf (SD)
- Leon Jünemann (SD)
- Nicolas Kolbenschlag (SD)
- Ingrid Münch (SD)
- Marcel Schöckel (SD)
- Philipp Kramer (SD)
- Sprint 3 release was successful with few adjustments.
- Use of 3 components for product accepted.
- User stories were discussed and appropriate changes were made.
Team + Wieland Eckert + Julia Krause + Giovanna Luisi
- Robert Balink (SM)
- Dev Darshan Kasthuri Umashankar (PO)
- Saber Jelodari (PO)
- Jens Wächtler (SD)
- Leander Tolksdorf (SD)
- Leon Jünemann (SD)
- Nicolas Kolbenschlag (SD)
- Ingrid Münch (SD)
- Marcel Schöckel (SD)
- Philipp Kramer (SD)
- Three dockers compile files, which build in local docker file. Do we have one compose for each separately?
- What is the ultimate goal? To be sure nothing is been forgotten.
- Checking the criteria for sprint 1.
- Checking the actual size of the issues with respect to the estimated size.
- Candidate tag should be created before the release tag can be created during the meeting.
- Create events in Discord to make the team more productive.
- Create channel for brain storming.
- Create pull request before feature board is done.
-
- The issue is assigned to Leander.
-
- The issue is assigned to Nicolas.
-
- The issue is assigned to Jan and Philipp.
-
- The issue is assigned to Jens.
-
- The issue is assigned to Ingrid.
Team + Wieland Eckert
- Robert Balink (SM)
- Dev Darshan Kasthuri Umashankar (PO)
- Saber Jelodari (PO)
- Jens Wächtler (SD)
- Leander Tolksdorf (SD)
- Leon Jünemann (SD)
- Nicolas Kolbenschlag (SD)
- Ingrid Münch (SD)
- Marcel Schöckel (SD)
- What does "Trigger on which channel, trigger levels, hysteresis" (from the project pdf) mean?
- Who is the release manager?
- Do we have just two components or three? With respect to the generator.
- Clarification about the generator?
- Discussion of release manager responsibility.
- Finalizing T-shirt design.
- Sharing ideas and opinions on “STARFISH RATIO”, to make our team more efficient.
-
- Poker planning for the issue, done by all the developers in the meeting.
-
- The issue is assigned to Leon and Nicolas, and Jens is the tester
-
- Poker planning for the issue, done by all the developers in the meeting.
-
- The issue is assigned to Marcel and Leander and Jan, and Jens is the tester.
-
- Poker planning for the issue, done by all the developers in the meeting.
-
- The issue is assigned to Ingrid and Philipp and Jens.
Discussion of tech stack.
- Jens Wächtler
- Leander Tolksdorf
- Leon Jünemann
- Nicolas Kolbenschlag
- Philipp Kramer
We discussed a tech stack which in our opinion suits the requirements:
- Generator
- Rust
- High Performance
- Good testability
- (any framework?)
- If the entry hurdle is too high, maybe switch to Java
- Rust
- Frontend
- JS + WebGL (framework)
- Cypress for end-to-end tests
- Maybe encapsulated by a high-level framework (React, Vue, Swelte)
- Maybe compiled to WASM for performance
- Docker
Teams:
- Generator
- Jens Wächtler
- Nicolas Kolbenschlag
- Leon Jünemann
- Frontend
- Leander Tolksdorf
- Philipp Kramer
- Marcel Schöckel
- Ingrid Münch
- Docker
- Leander Tolksdorf
- Marcel Schöckel
- Create a basic docker setup
- Create hello world generator
- Create hello world frontend
Team + Wieland Eckert
- Decided on name: SOSCI. Logo as homework
- Filled out Team contract
- Decision about rotating team meeting moderator postponed due to required input friom Mr. Riehle
- Team members should proactivly engage in issue assignments. The skill matrix will be used for identifiying issue assignments, but the team agreed that everybody can take up an issue on interest
- Standup mails will be sent flexibel and individually
- The team agreed on notifiying the each other in case of issues of any kind
- Scope of sprint:
- Team Contract
- Team Logo
- GitHub projects (Feature & Impediment) boards
- Team T-Shirt
- Wieland Eckert (Siemens Healthineers)
- Leander Tolksdorf (FU Berlin)
- Saber Jelodari (FAU Erlangen)
- Nicolas Kolbenschlag (FAU Erlangen)
- Marcel Schöckel (FAU Erlangen)
- Dev Darshan Kasthuri Umashankar (FAU)
Requirements:
- 10 Channels input
- Independent Y position control
- Sweep speed controllable on the frontend (cm/s)
- Grid (x: time, y: amplitude)
- ...
- Are there any tech stack requirements, e.g. a specific language?
- Browser: HTML and WebGL for the drawing
- Should main container and frontend be one docker container?
- Start with what's easier. In the beginning one container is enough.
- Requirements ragarding CI/CD?
- No special requirements besides the AMOS requirements
- Which format do messages have? Need complete specification of input data.
- There is no specification (but maybe some os specification)
- Does the generator generate randomly or does it have to have user input?
- Just create data and send it to the main container.
- Maybe later some parameters and ui could be nice.
- Frontend requirements:
- Vertical positioning should be implemented
- Time sweep adaption via frontend
- Continuously overwriting on previous data by timestep (Do not erase complete data on new cycle!)