...
- New Sprint AASIG Sprint 6 created
- let's start by defining a road map for this year
- We soon will have some milestones from the board meeting
- Discussion about what to do first. Suggestions:
- Road map for the project with what is needed from a technical point of view. Create priorities. Fix the sprint according to resources.
- Check the resources and decide what current tasks are being worked on
- Piotr shared his screen to check the current backlog and epics.
- let's go through the issues or tasks that are in-progress and check how we can close them or postpone them etc.
- AASIG-70: This will be closed soon (Piotr)
- AASIG-86: Are there any artefacts that we can present, do we go futher on this task → moved out of the sprint to the backlog
- AASIG-92: This is more interesting than AASIG-86 but more complex. Maybe we can be break it down to studies and overtime consider how to implement it. The first step seems doable though. The DOD (definition of done) is to define the API and protocol. maybe let's break it into sub-task to add DOD in the sub-task to show a diagram for example or a design, etc. → moved to the backlog.
First let's define the sub-task (in the next session AUDIO_HAL CW03)
- Proposal for the structure of the source code as seen in Android development repository structure (overview was given by Piotr Krawczyk: Could you please share the ppt when it's ready)
- we can have several repositories with manifest, with aasig_dev_configuration, and several repos depending on the services (vss, external audio mixing, vehicle plugin, etc.)
- downloading and building would be easily done.
- then we are modular and we can define the components that we would like to add to the build easily and we would share common parts.
- Together with Stephen: prepare action steps to prepare and implement this structure
- Gunnar will create the repos and support
- We also need to combine this with RENESAS build steps
- @All: Please have a look at the backlog to be prepared for the next meeting.
...