wklken / wklken/wklken.github.io
ELK 维护的一些点
Open
Nobody has claimed this yet.
2e5d40717a10e5262a193ae969538b7d
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/02/16/elk-about-upgrade.html and inspect the repository context for issue #88. The issue does not identify files, tests, requested changes, or a completion criterion, so the intended ELK maintenance work must be clarified before implementation.
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
- 15/100