Skip to content

Documentation Management ML3 #670

Closed
Closed

Description

@PandaeDo

Epic Description

Get the Documentation Management from ML2 to ML3

  • First the gaps in the process according to the definition in https://eclipse-score.github.io/process_description/main/ have to be documented in below list

  • deployment of process in one S-CORE module/platform repo, all documents are valid
    - [x] https://eclipse-score.github.io/score/main/platform_management_plan/documentation_management.html is in VALID state and shows usage of documentation mgt, e.g. documentation heade
    - [ ] Checklist is not used
    - [ ]

  • process requirements prio 1&2 "automation" are implemented in tooling
    - all "automation" requirements are implemented
    - gd_req__doc_attr_status is unclear as, 1. "invalid" state is not covered but exists, 2. valid(inspected) is for some workproducts but not for documents

  • respective tool evaluation done
    n/a

  • Safety Audit passed (no open deviations/actions)
    Presented in audit. All findings solved

Acceptance Criteria (DoD)

all identified gaps have been resolved

Activity

  1. self-assigned this
    on May 5, 2026
  2. added theissue type on May 5, 2026
  3. added this to the v0.9 milestone on May 7, 2026
  4. PandaeDo commented on Jul 14, 2026

    @PandaeDo
    ContributorAuthor

    For the reason that we changed the documentation in some aspects from score main to the modules I started with a first PR to integrate the documentation plan(s) in the modules. This is a proposal to gain experiences if this is useful. eclipse-score/persistency#305.

    Open question is if we should link from S-CORE to to module plans if we would agree on that.

  5. moved this from In Progress to Done in PRC - Process Development Communityon Aug 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentation

Type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions