Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Walk through the pre-work onboarding checklist end to end and record what breaks

オープン
  • 何か問題がありますか？
#171 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
45/100
issue の種類
ドキュメント
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
aws, github, markdown, terraform
領域
cloud, devops, documentation, infrastructure

調査の方向性

.github/ISSUE_TEMPLATE/pre-work-template-devops-security.md から始め、新しい pre-work issue で文字どおり実施し、リンクとミーティングの詳細を CONTRIBUTING.md、wiki、issue #163 と比較します。新たに見つかった各不具合を、その手順と期待される結果とともに記録します。テンプレートには明らかな修正だけを加え、より大きな判断は別の issue にリンクし、PR がマージされた後にチェックリストを再実行します。

索引モデルが issue の本文から書いたものです。

説明

complexity: medium Feature: Onboarding/Contributing.md role: DevOps Engineer size: 3pt
Overview

We need to confirm that the pre-work checklist a new member opens for themselves actually
works when followed literally, because nobody has run it start to finish since it was
written and we already know at least two of its links are wrong. A checklist that fails on
someone's first day is worse than no checklist, because it also teaches them that our
documentation cannot be trusted.

Action Items
  • Open a real pre-work issue from the template and follow it top to bottom, in order, as
    though you had never seen the repo. Do not skip a step because you already know the
    answer — the point is to find where a newcomer stops.
  • Record every failure as you hit it: dead links, wrong anchors, steps that assume access
    you were never granted, steps that are out of order, commands that error, and anything
    that needs knowledge the checklist never gave you.
  • Pay particular attention to the AWS steps. The checklist has the member create a personal
    AWS account, an IAM user and group, an S3 bucket and a DynamoDB table, then run
    terraform apply. Confirm this still reflects what we want a new member to do and that
    the cost warnings are accurate.
  • Confirm the meeting time in the checklist ("Wednesdays 6-8pm PST", no meetings on the 1st
    Wednesday) matches what the wiki says and what actually happens. These three sources
    currently disagree — see the sibling issue on the wiki meeting text.
  • Post your findings as a comment on this issue, one line per defect, each with the line it
    occurred on and what you expected instead.
  • For anything that is a quick, obvious correction, fix it in a PR against
    .github/ISSUE_TEMPLATE/pre-work-template-devops-security.md.
  • For anything larger or that needs a decision, open a separate issue and link it here
    rather than expanding this one.
  • After the PR merges, open one more fresh pre-work issue from the template and confirm the
    corrected links resolve. Template changes only render from the default branch, so this
    genuinely cannot be checked from your branch.
Resources/Instructions
  • Template under test: pre-work-template-devops-security.md
  • Target of most of its links: CONTRIBUTING.md
  • Two broken links are already known and ticketed as #163 — do not re-report or re-fix
    those two. This issue is the wider sweep for everything #163 does not cover.
  • Close the pre-work issue you opened for this walkthrough when you are done, so it is not
    mistaken for a real member's onboarding.
主要言語
HCL
スター
1
フォーク
14
平均マージ
3時間 36分
マージ済み PR（30日）
14

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

hackforla/devops-security のほかの issue

hackforla/devops-security の issue をすべて見る

似ている issue

Cloud の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。