Brushing up documentation of public methods
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 152
- Forks
- 95
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 10
Description
This issue has no 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
The issue names no files, tests, or entry points. Start by locating the documentation for the library's public methods and determine which methods need revision; the work is done when the relevant public-method documentation has been updated and reviewed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, ruby
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100