SW Dev Process Community - working slots

[aschemmel-tech]

Time:
Feb-18, 9-10 o'clock

Agenda:
Check participants
Align on Agenda for today

Planning - are we confident for Audit slot 3
Unique ID #180 - exception for standard requirements (question from Markus Schu) - no
Do we want to have safety/security attribute for roles? And also others like workflows and workproducts? See #329 - no, can be removed from roles, also only optional "security" attribute for stakeholder requirements.
Process description template (define what is in "concept", "getting-started" ...?
Other discussions from open PRs (e.g. #399)

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

Meeting Minutes:
Planning:

• Req - PR is available
• Arch - PR expected in 3-5 days
• Implementation - dicuss concept and working mode on Thursday
• Safety Mgt - PR available
• Verification - detailed planning in progess, transfer and fixing of findings should be achievable apart from some special topics with a lot of interdependencies

Present Requirement Process: #377 - findings documented in PR

Process description template - not for now to be able to do some improvements on the way, but "Requirement Process" should be used as an example.

[aschemmel-tech]

Time:
Feb-25, 9-10 o'clock

Agenda:
Check participants
Align on Agenda for today

Warnings stopping doc build
Inspection process (#432) to be discussed in workshop with Alexander Lanin, Jochen and AlexS
Verification (#441)
Implementation PR?
Discussions from other open PRs (e.g. #436)
Location for tutorials

Participants:
@aschemmel-tech
@hoe-jo
@kroehnd_mbg
@PandaeDo
@pahmann
@PhilipPartsch

Meeting Minutes:
Warnings stopping doc build - are switched on now
Implementation PR: Volker will publish today (even it will not build in the moment), potentially use workaround with "codespaces" - supported by Jochen
We agreed to restructure the landing page - Jochen to create a proposal to discuss
Invited to comment on #436
Verification: @pahmann to include concept and fix audit findings until friday, @PhilipPartsch to provide a template for feature/component integration testing template on pytest, we agreed to have test "specification" rather also as part of the "test" WPs

[masc2023]

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

Agenda:
Check participants
Align on Agenda for today

General Traceability Concept, #343
Change Management Draft, #443
#526 impl. Process
https://github.com/orgs/eclipse-score/discussions/434#discussioncomment-12299310

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

Meeting Minutes:

[aschemmel-tech]

Time:
Apr-1, 9-10 o'clock

Agenda:
Check participants
Align on Agenda for today

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

Meeting Minutes:
VDA Sys, Decide on Abstract, #806, fine for now
who is going to present? Discussed VDA-SYS presentation, speaker not decided yet, final call 04.04.2025, BMW will check internally

Release Management Ticket #313 may have to be taken over by other person, to be discussed on next Process Community Meeting

Alignment Eclipse Safety Process / Trustable SW / S-CORE / …
Discussed potential meeting with all stakeholder including Exida, Paul from CodeThink is in lead to organize it.

Alex gave Feedback from AUTOSAR workshop, outcomes: #809

Verification Process Tickets: https://github.com/eclipse-score/score/pulls?q=is%3Aopen+is%3Apr+label%3Acommunity%3Atesting

[PandaeDo]

Mar-25, 9-10 o'clock

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

Agenda:

• Verification levels
• Do we need different Roles regarding to the contributor e.g. if the contributor is able to perform a safety analysis?
• Shall we add Testing Community Member as Role?

Meeting Minutes:

• Philipp will create a proposal for recap of Component Test and Component Integration Test and also for argumentation of verification levels in the direction that we have integration test on component level caused of integration of units into components and sub-components into components.
  Roles
• Creation of additional roles in the codeowner table with enlarged skills e.g. Safety Engineer for Safety Analysis.
• Add Testing Community Member as Role.

[masc2023]

Apr-08, 2pm-3pm o'clock

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

Agenda:
Verification
Configuration Management, #845, postponed
Release Management, postponed
Quality Management, postponed

Meeting Minutes:
Discussed Verification, #721, #823

[masc2023]

Apr-15, 9-10 o'clock

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

Agenda:
Walk Through

Quality Management, #835
Safety Analysis
Configuration Management, #845
Security Management, #867

Meeting Minutes: