Document the release + contributing process
Open
Nobody has claimed this yet.
1. To develop
docs
enhancement
image
meta
- Dominant language
- Shell
- Stars
- 7.4k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
@tilosp @J0WI Have you thought about creating a CONTRIBUTING.md file for this repo, where people can learn how to contribute, how things are supposed to work, some basic info about the CI process? That would go a long way, I think :)
Originally posted by @marcelklehr in https://github.com/nextcloud/docker/pull/863#issuecomment-546637642
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Create CONTRIBUTING.md for the repository. Start by locating the existing release and CI process information, then document how to contribute, how the project works, and the basic CI workflow; done means newcomers can find all three areas in the new guide.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100