[Documentation] Could more explanations be added?

Open
#229 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
32/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby

Research direction

Start by browsing the repository's benchmark entries, especially their "conclusion" sections, and compare their explanations with the LFS/BLFS project referenced in the issue. Done means adding concise, understandable explanations of what most benchmark results mean and why they matter; the issue does not identify specific files or tests.

Written by the indexing model from the issue text.

Description

Hey there,

You lot provide tons of benchmarks. This is nice. But often I don't know what this really
means. Would it be possible to add one or two sentences to most benchmarks out
there? In particular "conclusion" - this would help understand the situation better.

This does not have to be long, as said, a sentence of regular length should suffice for
most. Right now there is very little documentation and explanation, so people have
a hard time learning the "why"'s. See the LFS/BLFS project in how to explain things
so normal people can understand stuff better.

Dominant language
Ruby
Stars
5.7k
Forks
370
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fastruby/fast-ruby

All issues in fastruby/fast-ruby

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.