Create inventory of concepts lacking exercises

Open
#1,906 24 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
content

Research direction

Start by inspecting the repository's exercise metadata and the practices fields described in the issue. Decide whether the inventory should list every exercise and concept or only concepts with few or no exercises. Done means producing a complete, usable inventory for track maintainers, with its scope clearly documented.

Written by the indexing model from the issue text.

Description

discussion

Exercism v3 Practice Exercises (of which most are implementations of exercises in this repo) have a practices field.
This field list the concepts that can be practiced in that exercise.
What several maintainers found was that for concepts, there are very few exercises that can be used to practice that concept.
One example concept that comes to mind is dates, for which we have (out of the top of my head) just two exercises: meetup and gigasecond.
Contrast that with the number of string exercises (anagram, isogram, pangram, bob, the song-related exercises, and so on).

The idea of this issue is to somehow compile a list of those concepts we feel could benefit from having more exercises.
We can do this several ways:

  1. Create a list with all exercises and their concepts.
  2. Create a list with the concepts with few (or no) exercises

The first option is a lot more work, but would have the benefit that it could be used as a reference for track maintainers when choosing an exercise to implement.
The second option is easier to do.

I'd be curious in hearing your opinion.

Dominant language
Ruby
Stars
362
Forks
566
Avg merge
15h 13m
Merged PRs (30d)
8

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 exercism/problem-specifications

All issues in exercism/problem-specifications

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.