Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Create a pre-work onboarding issue template for general DevOps CoP members

Aperta
#195 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
57/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github, markdown
Ambito
devops, documentation

Direzione di ricerca

Inizia esaminando .github/ISSUE_TEMPLATE/pre-work-template-devops-security.md e i template devops esistenti, quindi conferma con i lead le aspettative generali per i membri. Crea il template markdown self-service in .github/ISSUE_TEMPLATE/, aggiorna config.yml se necessario e mantieni fuori i passaggi AWS/Terraform. Il lavoro è completato quando il template mergiato appare nel New issue picker su master e crea un issue con le etichette corrette.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

complexity: medium feature: templates role: DevOps Engineer size: 3pt
Overview

We need an onboarding issue that a new DevOps CoP member can open for themselves, because right
now one does not exist. devops has templates only for onboarding and offboarding leads, and
those are performed by an existing lead rather than by the newcomer. devops-security has a
self-serve pre-work checklist, but it is specific to that repo and takes the member through
creating a personal AWS account and running Terraform. A person who joins the CoP and is not
going to work on devops-security therefore has no onboarding issue at all, and nothing tracks
whether they ever got set up.

Action Items
  • Confirm with the leads what a general CoP member is actually expected to do in their first
    two weeks. This is the part that needs a decision, not just drafting — the answer
    determines everything below.
  • Write the template into .github/ISSUE_TEMPLATE/ as a markdown template, following the
    shape of devops-security's pre-work template: self-assign, pick a role label, set status,
    add to the board, attend the meeting.
  • Set labels: in the frontmatter. Note devops has no equivalent of devops-security's
    complexity: prework label — decide whether to add one or use complexity: small.
  • Keep the AWS and Terraform steps out. If a member later joins devops-security work, they
    open that repo's pre-work issue then. Link to it rather than duplicating it.
  • Add the template to .github/ISSUE_TEMPLATE/config.yml if that file gates what appears in
    the picker.
  • After the PR merges, go to the repo's "New issue" page and confirm the template appears and
    produces a correctly labelled issue. GitHub renders the picker from the default branch
    only, so this cannot be verified from your branch.
Resources/Instructions
  • Shape to follow: pre-work-template-devops-security.md
  • What devops has today: onboard-ops-cop-lead.md, offboard-ops-cop-lead.md,
    recruit-new-lead.md, post-an-open-role.md, plus the two blank forms — none of them is a
    member self-onboarding issue
  • The default branch of devops is master, not main
  • This template is what the team-side checklist (sibling issue) will point new members at, so the
    two should agree on what the member is asked to do
Lingua principale
PowerShell
Stelle
8
Fork
10
Merge medio
7h 30m
PR unite (30g)
22

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di hackforla/devops

Tutte le issue di hackforla/devops

Issue simili

Altre issue su DevOps

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.