Conversation
|
just copied the current templates from https://github.com/eclipse-score/score repository |
Did you check https://github.com/eclipse-score/module_template/pull/41/changes ? If not needed any more I can close https://github.com/eclipse-score/module_template/pull/41/changes |
masc2023
left a comment
masc2023
left a comment
There was a problem hiding this comment.
Initial take over of existing templates for the whole platform,, https://github.com/eclipse-score/module_template/pull/41/changes will be used for further improvements. After achieving that, .github may then updated
|
@FScholPer , @masc2023 I did my best, checked it on my playground and it works for the whole organization. :-) |
masc2023
left a comment
masc2023
left a comment
There was a problem hiding this comment.
Needs discussion, please organize Meeting, also invite @aschemmel-tech , old templates used in Safety Audit, changes have impact on process adaptions
There was a problem hiding this comment.
You change major thins define in Change Management Process, needs discussion and would have influence of Process
There was a problem hiding this comment.
You change major thins define in Change Management Process, needs discussion and would have influence of Process, Further Component Request Missing
|
|
|
masc2023
left a comment
masc2023
left a comment
There was a problem hiding this comment.
See comment, @aschemmel-tech , please review and give comment, we need to close that now soon, because it will lead to an rework of Change Management, otherwise we can not meet v0.7
There was a problem hiding this comment.
Feature and Component Request lack both the Change Management topics, Modification deleted and Impact Analysis, if we introduce another issue type, as proposed, Change Feature/Component, with the original fields I would agree
There was a problem hiding this comment.
In my understanding also the introduction of a new feature would need a change impact analysis, or not?
aschemmel-tech
left a comment
aschemmel-tech
left a comment
There was a problem hiding this comment.
See inline comments - main point is how to document the Change Impact Analysis
| options: | ||
| - QM | ||
| - ASIL_B | ||
| - ASIL_D |
There was a problem hiding this comment.
we should not have ASIL_D - this is not supported at the moment. Also in the other templates.
| attributes: | ||
| label: Expected Implementation Version (Release) | ||
| options: | ||
| - '1.0' |
There was a problem hiding this comment.
is this maybe a bit too coarse?
| attributes: | ||
| label: Component Request Description | ||
| description: | | ||
| - Follow the [Change Management Workflow](https://eclipse-score.github.io/score/main/platform_management_plan/change_management.html#change-request-workflow) |
There was a problem hiding this comment.
Is your intention to say "All changes to features and components are planned with this ticket type"?
| attributes: | ||
| label: Component Request Description | ||
| description: | | ||
| - Follow the [Change Management Workflow](https://eclipse-score.github.io/score/main/platform_management_plan/change_management.html#change-request-workflow) |
There was a problem hiding this comment.
Without an explicit link to the Change Impact Analysis I doubt this will be done.
|
Thanks for putting effort into improving the templates. For infrastructure, though, these don’t work well in practice. We’ve repeatedly seen that mandatory templates discourage people from opening issues at all. The major reason for poor planning is that people refuse to fill out these templates. I’d really like us to prioritize usability here. If creating an issue feels heavy or bureaucratic, people simply won’t do it — and that hurts transparency more than it helps compliance. Maybe we can aim for a lightweight default template WITHOUT FIELDS that lowers the barrier while still collecting useful information? |
|
On second thought I have an even better argument: obviously modules / dependable elements need to follow the process much closer than a tool. Please try out the new templates in a module / dependable element repo, and collect feedback there. |
4 participants
pre-work for eclipse-score/score#2382