SW Dev Process Community - working slots #526 Implementation process description

[PandaeDo]

Time:
Mar-07, 11-12 o'clock

Agenda:
Deep dive into the implementation process description.
Plan next steps regarding audit on 18th

Participants:
@aschemmel-tech
@hoe-jo
@kroehnd
@masc2023
@PandaeDo
@pahmann
@vinodreddy-g

Meeting Minutes:
#526

Overview of Implementation Process Description and more detailed at in the Concept Description. The following points are related on remarks and discussions.

• Getting started: Change all the remarks as draft approaches or link to issues/discussions to have a starting point for the Audit
• Getting started: The compiler must not be certified. It's used as a development tool to use e.g. compiler warnings. The qualified compiler from QNX shall mentioned as highly recommended after it's available.
• Getting started: Link to SW Development plan. Placed under More/PMP
• Example Detailed Design: Add textual description what will be inside of box like "Placeholder for the description that will be generated from doxygen"
• Workflow: Adaption on example from concept description
• Guidance/Checklist: Use inputs from incubator project
• Guideline: Refer to coding guidelines
• Workflow: Update responsible and approver to committer
• Workproducts: Code inspection overtake from general description. Rename it to "Code and Detail Inspection"
• Concept: Remark to "class diagrams" in the description of static view shall be deleted. We didn't use the expression of class diagrams in your model
• Workflow: Workflow "create/perform unit test" delete. It will be integrated in validation

The remarks and outputs of the discussions will be implemented in the approach. The Guidances for C++, Phyton will be commited by Jochen as a draft. Parallel the reviews could be started.

[masc2023]

Time:
Mar-10, 11-12 o'clock

Agenda:
Deep dive into the verification process description, #441
PR to be merged today, remove ToDos to Issues
Plan next steps regarding audit on 18th

Participants:
@aschemmel-tech
@hoe-jo
@masc2023
@PandaeDo
@pahmann

Meeting Minutes here: https://github.com/orgs/eclipse-score/discussions/617

[masc2023]

Time:
Mar-11, 9-10 o'clock

Agenda:
Audit Agenda
Review again, #526 , Implementation Process

Participants:
@aschemmel-tech
@hoe-jo
@masc2023
@PandaeDo
@markert-r
@pahmann
@PhilipPartsch

Meeting Minutes:
Agenda for Audit for 18.03.2025 discussed and agreed
@aschemmel-tech will check the Audit Findings for completeness, #537
Future improvement, to be tool agnostic, improvement ticket created, #630
@PhilipPartsch proposed to link directly from Sphinx-Need into Code, will update the PR of process implementation
@PandaeDo will invite for another working slot, proposal participants, @hoe-jo, @aschemmel-tech, @masc2023, 13-14

[masc2023]

Time:
Mar-11, 13-14 o'clock

Agenda:
Deep dive into the implementation process description.
#526

Participants:
@aschemmel-tech
@hoe-jo
@masc2023
@PandaeDo

Meeting Minutes:

• Delete link at getting started to build-checks and refer to readme
• SW Dev Plan is located under docs/platform_management_plan
• Input of SW Dev Plan is incorrect
• SW Dev Plan is the input for Detail Design
• Use automated checks whenever it's possible. Control checklist