Process Development Community [2025-03-27]

[masc2023]

Agenda:
Check participants and introduce new members
Align on Agenda for today

Feedback from Project Planning Meeting, Check Correct Epic Status, Linked Issues
Discuss Support Coding Guidelines form Process Team, Rust (@pandoe, @masc2023), C++ (@hoejoe, t.b.d.), Phyton (@AlexanderLanin )
Discuss #760
Some open topics to be planned in the next meeting, #310, #315, and important #710, #541
Plan, Discuss ongoing PRs, Activities

Participants:
@PandaeDo
@hoe-jo
@masc2023
@pahmann
@markert-r

Meeting Minutes:

#760 discussed,
C++ Process Pilot is LoLa, supported by @hoe-jo, @aschemmel-tech, @LittleHuba, Sub-Issue will be created to link it to this EPIC, consider also here the Coding Guide lines for C++ (@hoe-jo , @aschemmel-tech, @LittleHuba)
Rust Process Pilot is FEO, discuss in the next Monday Meeting, discuss with @ramceb, consider also here the Coding Guide lines for Rust

Release Management, Tool Management, Safety Analysis Process should be discussed on Monday Meeting

Discussed Review Findings from Dan below, decided @PandaeDo will coordinate the finding resolution

[PandaeDo]

• Dan finished his Review as a adopter to show first findings Process Model review #744 (comment). How we would use this input?
• Lars tried to improve contribution description docs: improved how to contribute section #776 (review). The reason was the questions from Valeo how to contribute. After review it I think it might be helpful to improve the description for a stakeholder that want's to contribute. Improvement: Description of "Contribute" #789