-
Notifications
You must be signed in to change notification settings - Fork 187
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #5916 from owncloud/add_new_services_checklist
[docs-only] New service checklist for owncloud.dev
- Loading branch information
Showing
1 changed file
with
37 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
--- | ||
title: New Service Checklist | ||
date: 2023-03-23T00:00:00+00:00 | ||
weight: 0 | ||
geekdocRepo: https://github.com/owncloud/ocis | ||
geekdocEditPath: edit/master/docs/services | ||
geekdocFilePath: new-service-checklist.md | ||
geekdocCollapseSection: true | ||
--- | ||
|
||
When a new service gets introduced, this checklist is a good startingpoint for things that need to be completed before the service gets published (merged). This list is without claim of completeness or correct sort order. | ||
|
||
## New Service Checklist | ||
|
||
Use this checklist with copy/paste in your PR - right from the beginning. It renders correctly in your PR. | ||
|
||
```markdown | ||
- [ ] Provide a README.md for that service in the root folder of that service. | ||
- Use CamelCase for section headers. | ||
- [ ] For images, you currenly have to create a folder named `images` on the same lavel where readme.md is located and put all the images used in readme.md. For the time being, the imagefolder needs to be manually copied to `docs/servcies/<service name>`. This is also true for image changes post merging. | ||
- [ ] If new CLI command are introduced, that command must be described in readme.md. | ||
- [ ] Add the service to the makefile in the ocis repo root. | ||
- [ ] Make the service startable for binary and individual startup: | ||
- For single binary add service to `ocis/pkg/runtime` | ||
- For individual startup add service to `ocis/pkg/commands` | ||
- [ ] Add the service to `.drone.star` to enable CI. | ||
- [ ] Inform doc team in an _early stage_ to review the readme AND the environment variables created. | ||
- The description must reflect the behaviour AND usually has a positive code quality impact. | ||
- [ ] Create proper description strings for envvars - see other services for examples, especially when it comes to multiple values. This must include: | ||
- base description, set of available values, description of each value. | ||
- [ ] When suggestable commits are created for text changes and you agree, collect them to a batch and commit them. Do not forget to rebase locally to avoid overwriting the changes made. | ||
- [ ] If new envvars are introduced which serve the same purpose but in multiple services, an additional envvar must be added at the beginning of the list starting with `OCIS_` (global envvar). | ||
- [ ] Ensure that a service has a debug port | ||
- [ ] If the new service introduces a new port: | ||
- the port must be added to [port-ranges.md](https://github.com/owncloud/ocis/blob/master/docs/services/port-ranges.md) and to the readme.md file. | ||
- [ ] Make sure to have a function `FullDefaultConfig()` in `pkg/config/defaults/defaultconfig.go` of your service. It is needed to create the documentation. | ||
``` |