| ... | ... | @@ -25,7 +25,7 @@ The Onboarding makes sure that new members are welcomed and where to find releva |
|
|
|
## Adding projects
|
|
|
|
The workflow starts with adding new projects for the review. You will start this process by cloning the project into our repository as described below.
|
|
|
|
|
|
|
|
First of all the [requirements for application](/2-Guides/application-guide.md) have to be checked. If everything is fullfilled the project can directly step in the review stage. If there are still open questions the project can be added as development project, helping the applicants to get everything ready for review.
|
|
|
|
First of all the [requirements for application](/2-Guides/application-guide) have to be checked. If everything is fullfilled the project can directly step in the review stage. If there are still open questions the project can be added as development project, helping the applicants to get everything ready for review.
|
|
|
|
|
|
|
|
### Overview
|
|
|
|
Start by adding the project to the [Assessment overview](https://gitlab.opensourceecology.de/verein/projekte/cab/CAB/-/blob/main/archive/assessments.md) and set the status to "development" or "in progress" accordingly (see above). This will show everyone the projects that are or have been undergoing the assessment by OSEGeV.
|
| ... | ... | @@ -80,9 +80,9 @@ git checkout -b review |
|
|
|
Eventually you may want to protect the reviewer branch, so reviewers (with developer rights) can only enter changes by merge requests. Additionally the release tag can be set as protected.
|
|
|
|
|
|
|
|
#### Add Review Issues
|
|
|
|
Add the Review Issues as described in the [Template Guide](2-Guides/issue-templates-guide.md).
|
|
|
|
Add the Review Issues as described in the [Template Guide](2-Guides/issue-templates-guide).
|
|
|
|
|
|
|
|
The next step towards the assessment will be to create the initial issues for review. Therefore continue with the [template-guide](/2-Guides/issue-templates-guide.md). Eventually you might want to add some members first:
|
|
|
|
The next step towards the assessment will be to create the initial issues for review. Therefore continue with the [template-guide](/2-Guides/issue-templates-guide). Eventually you might want to add some members first:
|
|
|
|
|
|
|
|
## Adding members
|
|
|
|
Add new members to the project. Start by adding members as guest in the [CAB Group](https://gitlab.opensourceecology.de/verein/projekte/cab), so they can be found within the sub-projects. The following roles and access rights are used within the CAB:
|
| ... | ... | @@ -125,13 +125,13 @@ Hint: In theory it is possible that some else then the assigend reviewers sets t |
|
|
|
# Quick Check
|
|
|
|
Short checklists for the CAB-Admin tasks.
|
|
|
|
## Add new project
|
|
|
|
- Check [requirements for application](/2-Guides/application-guide.md)
|
|
|
|
- Check [requirements for application](/2-Guides/application-guide)
|
|
|
|
- Add project in [Assessment overview](https://gitlab.opensourceecology.de/verein/projekte/cab/CAB/-/blob/main/archive/assessments.md)
|
|
|
|
- Create [Assessment][projectname] issue in [Project Assessment Milestone](https://gitlab.opensourceecology.de/verein/projekte/cab/CAB/-/milestones/3)
|
|
|
|
- Clone the project into https://gitlab.opensourceecology.de/verein/projekte/cab
|
|
|
|
- (Name the project like in original, adding the version number )
|
|
|
|
- Create and fill the [assessment header](https://gitlab.opensourceecology.de/verein/projekte/cab/CAB/-/blob/main/Templates/assessment-header.md) in the readme
|
|
|
|
- Eventually add new members, then continue with [template-guide](/2-Guides/issue-templates-guide.md)
|
|
|
|
- Eventually add new members, then continue with [template-guide](/2-Guides/issue-templates-guide)
|
|
|
|
|
|
|
|
## Add new member
|
|
|
|
- Send the interested member the member-form and have it filled
|
| ... | ... | |
