| ... | ... | @@ -28,7 +28,7 @@ The workflow starts with adding new projects for the review. You will start this |
|
|
|
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.
|
|
|
|
|
|
|
|
### Overview
|
|
|
|
Start by adding the project to the [Assessment overview](/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.
|
|
|
|
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.
|
|
|
|
|
|
|
|
Next create an Issue in the [Project Assessment Milestone](https://gitlab.opensourceecology.de/verein/projekte/cab/CAB/-/milestones/3) named [Assessment][projectname]. This way our community will have an overview of the projects that are currently perparing for or undergoing assessment.
|
|
|
|
|
| ... | ... | @@ -69,7 +69,7 @@ git push -u origin --all |
|
|
|
git push -u origin --tags
|
|
|
|
```
|
|
|
|
#### Assessment Header
|
|
|
|
Add and fill the [assessment header](/Templates/assessment-header.md) (in Folder [Templates](/Templates)) at the top of the readme file.
|
|
|
|
Add and fill the [assessment header](https://gitlab.opensourceecology.de/verein/projekte/cab/CAB/-/blob/main/Templates/assessment-header.md) (in Folder [Templates](https://gitlab.opensourceecology.de/verein/projekte/cab/CAB/-/blob/main/Templates)) at the top of the readme file.
|
|
|
|
|
|
|
|
### Projects in Review Stage
|
|
|
|
Projects for assessment will use two different branches. The original files will be in the **main branch**. The assessment will take place in the **review branch**. Once it is finished the review branch will be merged into the main issue using the final tag.
|
| ... | ... | @@ -126,11 +126,11 @@ Hint: In theory it is possible that some else then the assigend reviewers sets t |
|
|
|
Short checklists for the CAB-Admin tasks.
|
|
|
|
## Add new project
|
|
|
|
- Check [requirements for application](/2-Guides/application-guide.md)
|
|
|
|
- Add project in [Assessment overview](/archive/assessments.md)
|
|
|
|
- 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](/Templates/assessment-header.md) in the readme
|
|
|
|
- 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)
|
|
|
|
|
|
|
|
## Add new member
|
| ... | ... | |
