建议将官方文档放到 git 上维护
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.8k
- Forks
- 282
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 1
Description
- 更加公开透明，文档大家一起维护，众人拾柴火焰高
- 维护文档的人，也可以在committer中出现
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
Review how the official documentation is currently maintained and where it is published. Define the proposed Git-based workflow, contribution process, and committer responsibilities; the issue is done when the maintainers agree on an actionable plan.
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