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

Write the checklist of what the team does for a new member, and publish it on the wiki

Abierto
#194 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
65/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github
Área
documentation

Línea de trabajo

Empieza comparando .github/ISSUE_TEMPLATE/onboard-ops-cop-lead.md, hackforla/devops#30, hackforla/incubator#27, la página wiki existente de team-lead y el DevOps CoP Roster. Verifica cada paso de onboarding y cada enlace con respecto a la realidad actual. Después, publica la checklist de miembros validada en la página wiki elegida, enlázala desde Home bajo “Joining the DevOps team” y haz que un Lead no involucrado confirme que es suficiente.

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

Descripción

complexity: medium feature: Onboarding role: CoP lead size: 2pt
Overview

We need one written checklist of everything the team has to do when someone joins, so that
onboarding does not depend on whichever lead happens to pick it up remembering all of it. A
checklist exists for onboarding a CoP lead and one exists on the incubator side for team
members, but there is nothing for a general DevOps CoP member, and neither of the existing two
is on the wiki where a lead would look for it.

Action Items
  • Draft the checklist. At minimum it must cover:
    • Adding them to the right GitHub teams. Note the org has five: devops-read,
      devops-write, devops-merge, devops-maintain, devops-admin. Say which ones a new
      member gets by default and who can grant them.
    • Getting them onto the roster — the existing incubator checklist splits this into "send",
      "team member adds themselves", "check for public", which is worth copying because the
      middle step is the one that gets forgotten.
    • Pointing them at their onboarding issue, and being explicit about which one.
    • Slack #ops, the Google Calendar invite, Google Drive, and 1Password — copy the
      structure from the lead checklist rather than inventing a new one.
  • Confirm each step against reality before writing it down. Do not copy a step from the lead
    checklist without checking it still works — at least one link in that checklist is already
    dead (see the sibling issue on the 404 team link).
  • Decide where the canonical copy lives: a new wiki page, or an addition to
    Onboarding Process for Project Team Leads.
    That page is currently incubator-flavoured, points at a closed issue, and has an empty
    "Project's GitHub team URL" field, so it needs attention either way.
  • Publish it on the wiki and link it from Home under "Joining the DevOps team".
  • After it is published, ask a lead who did not write it to read it and confirm they could
    onboard someone from it alone.
Resources/Instructions
Lenguaje dominante
PowerShell
Estrellas
8
Forks
10
Merge medio
7 h 30 min
PR fusionados (30 d)
22

Guía de contribución

Abrir la 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 hackforla/devops

Todos los issues de hackforla/devops

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.