Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Human onboarding proof from a clean clone, by two teammates (H1)

Abierto
  • ¿Algo no está bien?
#105 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
playwright, typescript
Área
testing-qa

Línea de trabajo

Start with the H1 entry in the human-tasks.md handoff catalogue and the onboarding docs it refers to. Complete team-orientation, then have two teammates who did not build usabl independently go from a fresh clone to their first honest verdict, logging confusion separately. Done means both complete within 30 minutes with only the listed human actions and their confusion points are recorded.

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

Descripción

area: setup enhancement human task

The agent ran a proxy for this in v0.2.0 (demo readiness D2). The real proof is teammates who have never wired usabl doing it from a clean clone.

  • Why: confirm the onboarding path holds for real people, not only an agent proxy. One person getting through can be luck, prior context, or a lucky machine. Two independent runs are the smallest evidence that the path itself works.
  • Owner: two teammates who did not build usabl, working independently and not comparing notes until both are finished.
  • Prerequisite: onboarding docs are current (done in v0.2.0).
  • Acceptance: each of them goes from a fresh clone to first honest verdict, with only review, merge, and one approved repo setting as the human acts, under 30 minutes. Every point of confusion is logged separately, so it is visible whether the two hit the same wall or different ones.
  • Target: v0.2.1.

Prerequisite for every human task: complete team-orientation first (usabl-dev.github.io/usabl/team-orientation.html), so the owner shares the result model, the four surfaces, and the claim boundary.

Source: human-tasks.md handoff catalogue (H1).

Lenguaje dominante
TypeScript
Estrellas
0
Forks
0
Merge medio
2 h 48 min
PR fusionados (30 d)
8

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

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 usabl-dev/usabl

Todos los issues de usabl-dev/usabl

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.