Doc: How close do we stick to upstream docs?
Open
area/docs
kind/enhancement
team/cli
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
Vincent tells me that these are just copied from the upstream. I guess it's an issue for another day what we do when the upstream docs aren't as detailed as we might like or have stylistic differences.
/lgtm
_Originally posted by @ewollesen in https://github.com/aws/eks-anywhere/pull/2149#pullrequestreview-971519299_
Contributor guide
Research direction
No files, tests, or entry points are named. Start by reviewing the upstream documentation and the repository’s copied documentation, then determine how differences in detail and style should be handled. Done means the project’s policy is decided and documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100