Maintainers: A new "Approaches" repository?

Abierto
#2,704 21 comentarios 8 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Ruby
Estrellas
362
Forks
566
Merge medio
15 h 13 min
PR fusionados (30 d)
8

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de exercism/problem-specifications

Todos los issues de exercism/problem-specifications

Issues similares

Más issues de Ruby

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.