Maintainers: A new "Approaches" repository?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- documentation
Research direction
Read the issue discussion and the linked preview to understand the proposed centralized approaches repository and its scope. The issue asks for thoughts or concerns; it does not define an implementation task or acceptance criteria, so there is no specific change a contributor can complete yet.
Written by the indexing model from the issue text.
Description
Hi @exercism/track-maintainers!
Many of you will remember that a while ago we add "Approaches" to Exercism, where solutions get tagged with the type of approach they've taken. These are linked to Dig Deeper documents.
Some tracks made some good progress on some exercises, but we never got enough coverage that we could really add this as a first-class citizen of exercism like I wanted. Now, with the help of LLMs, we can automatically segment solutions into approaches, tag solutions when they're submitted and provide interesting insights for students about other paths they can take. I'm currently working on revamping the exercise/solution pages to add this and other new features, and as part of that I'll generate approaches for all exercises on Exercism.
One consequence of this is that I'll also be generating lots of approach documents, which explain that approach and it's pros/cons. Previously, these have lived inside track repos, but as we're going to be making them en mass, this would involve many thousands of new md files being added to repos. A bit like the i18n work, I think will be a bad experience for maintainers, so I'm proposing adding a new top-level repo for approaches, moving existing approach/dig-deeper content into there from repos, and managing it centrally. Anyone can PR improvements and I'll set something up so track-maintainers PR's get auto-checked and merged agentically.
If anyone has any thoughts/concerns before I do this, please let me know 🙂
PS: Here's a little preview of the sort of grouping and "dig deeper" content that I'm generating (click the "Read More"s). This is just my experimentation space and now how it will appear in the website.
- 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
- 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.
More from exercism/problem-specifications
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
exercism/problem-specifications#2686 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 35/100
exercism/problem-specifications#2153 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
exercism/problem-specifications#2120 · 7 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
exercism/problem-specifications#2108 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
exercism/problem-specifications#2083 ·
Maintainers usually reply within 1 day
All issues in exercism/problem-specifications
Similar issues
-
開発用DockerイメージにPlaywrightのシステム依存を追加するPossibly taken @momocus claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
sakazuki-org/sakazuki#1453 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
jenkins-infra/jenkins.io#9615 · 1 comment ·
Maintainers usually reply within 1 day
-
fix(ocr): compile the Tesseract-free pipeline with Tokio runtimePossibly taken @Goldziher claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Metric tooltips that contradict how the metric is calculatedPossibly taken @aniadeadu claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
WikiEducationFoundation/WikiEduDashboard#7303 · 1 comment ·
Maintainers usually reply within 1 day
-
WhatsApp Cloud template sync saves a partial template list when one page of the Graph API response failsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days