LinuxSuRen / LinuxSuRen/open-source-best-practice
思考：如何避免让好的 issues 石沉大海？
Open
Nobody has claimed this yet.
- Dominant language
- Smarty
- Stars
- 416
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
当社区用户提了一些 issues 后，可能长时间都没有人来响应，但有一些可能还是比较有价值的。
对 issues 响应慢，甚至石沉大海的坏处可能有：
* 可能会打击贡献者的积极性
* 社区也有可能会失去某些很有价值的 issues
这些issue如果有人互动起来的话，有可能让更多的贡献者参与进来。然而对于这类issue，社区贡献者可能会感觉到很无奈，找不到很好的办法。
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
No files, tests, or entry points are named; start by reviewing the issue's concerns and the repository's existing open-source practice content. The issue defines no concrete change or completion criteria, so the proposed response process and its documentation location would need agreement before work could be considered done.
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