wklken / wklken/wklken.github.io
ELK维护的一些点(二)
Open
Nobody has claimed this yet.
a4b1ad07828941a8ae16aa49d0a8b26f
Gitalk
- Dominant language
- HTML
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
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
Start by reading the linked article at https://wklken.me/posts/2016/05/07/elk-about-2.html and inspect the repository's corresponding blog content. Identify which maintenance points are intended for this issue and which files they affect; the work is complete only once a concrete scope and verifiable edits are defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100