search

International-Data-Spaces-Association / IDS-RAM_4_0

Focusing on the generalization of concepts, functionality, and overall processes involved in the creation of a secure 'network of trusted data' , the IDS-RAM resides at a higher abstraction level than common architecture models of concrete software solutions do. The document provides an overview and dedicated architecture specifications.
Creative Commons Attribution 4.0 International
38 stars 27 forks source link

4.2. Revision Workflow #127

Closed mokamhuber closed 2 years ago

mokamhuber commented 2 years ago

As discussed in our meeting last week, we have assigned a responsible editor and reviewer for each section: 4.2. Introduction: @mohuber (Editor), @nadjamenz (Reviewer) 4.2.1. Certification Aspects: @mohuber (Editor), @ssteinbuss (Reviewer) 4.2.2. Roles: Andreas Teuscher (Editor), Pedro Pinto (Reviewer) 4.2.3. Operational Environment Certification: Jonas Winkel (to be confirmed, fall-back: @nadjamenz), @gboege (Reviewer) 4.2.4. Component Certification: @nadjamenz (Editor), @gboege (Reviewer) (4.2.5. Processes) 4.2.5.1. Approval Process: @aliasimon (to be confirmed), Fallback&Review: @Sonia-IDSA & @mohuber 4.2.5.2. Certification Process: @Sonia-IDSA (Editor), Pedro Pinto (Reviewer)

There is (at least) one issue for each section in the RAM Certification perspective. The responsibilities (editor & reviewer) were added to the respective issues in the Repo. Initially, each issue is assigned to the editor. Each editor shall open a separate branch for their section (which can be done directly from the editor if done in the web GUI) naming it after the issue and task as described in the contribution guidelines: https://github.com/International-Data-Spaces-Association/IDS-RAM_4_0/blob/main/CONTRIBUTING.md#branches)

As soon as editors are finished with the content and want to start the review phase, they open a pull request for their section and assign the reviewer as well as @mohuber and @ssteinbuss

Deadline: both editing and review needs to be finished by the end of February If you have any issues with the Git workflow, please comment here or reach out to @mohuber and @ssteinbuss

In case other people (e.g., @aitorce, Olivier) are willing to support as well, just reach out and we'll surely find some way for you to assist with or take over tasks :)

mokamhuber commented 2 years ago

today in the meeting on the IDS RAM 4.0 status, we discussed at what point in time pull requests should be opened and we agreed that it would be useful to have an open pull request as soon as an editor has started their work to enable others to see the progress and maybe comment on open points. So, please always directly open a pull-request when you start work at your section but mark the pull-request as a draft while it is not yet ready to be reviewed.