LinuxSuRen / LinuxSuRen/open-source-best-practice
思考：PR 的 review 过程中，如何证明自己的观点？
Nobody has claimed this yet.
- Dominant language
- Smarty
- Stars
- 416
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
* 很明显的、约定的观点，需要证明吗？
* 这里，关键在于“很明显”、“约定的”这样的结论是谁下的。某个人觉得是“约定的”，不代表其他人也这么认为。那么，总是有一些公开的、公认的资料可以查询，例如：[维基百科](https://zh.wikipedia.org/wiki/Wikipedia:%E9%A6%96%E9%A1%B5)。
* 我“感觉”某个地方不对、不合适，该怎么提 PR 或者 comment？
* “感性”的回答，可能很难得出一致的讨论结果。我们需要尽可能给出“理性”的证据来证明自己的观点。
* 如何防止 review 过程中有无限的 comment 持续发生的
* 热烈讨论，不代表应该无限去讨论。因此，讨论的技巧、取舍、妥协都是需要的。
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points to inspect. First clarify whether it should become a concrete documentation change; done would require an agreed scope and acceptance criteria for the review guidance.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100