Use tidb-dev-guide as contribution guide?
Open
@TomShawn is already working on this.
Since Nov 24, 2021.
area/general
tracked
- Dominant language
- Python
- Stars
- 617
- Forks
- 724
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 223
Description
I'd suggest we use tidb-dev-guide as docs contributing guide. So only one copy need to be maintained. And in tidb-dev-guide, there are many more content for the entire TiDB community.
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.
Assessment
This issue has not been assessed yet.