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

Update repo to include Github Projects

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

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

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
20/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
停滞
技術スタック
github
領域
tooling

調査の方向性

まず issue #109 を読み、この issue にある簡略化および変更された列リストと、そこで提案されているワークフローを比較します。ファイルやテストは指定されていません。完了とするには、合意されたプロジェクトワークフローと、選択した列で構成されたリポジトリの GitHub Project が必要です。

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

説明

discuss

In #109, @nelsonic proposed the following columns:
tcm-workflow-with-blockers

  • Ideate: Define User Story
  • Create UX/UI Wireframe/flow
  • Tech Spec (add checklist)
  • Estimate Time
  • Ready for Dev
  • In Development
  • Ready for Review
  • In Review (Pull Request)
  • Ready for Test
  • In Test
  • Ready for Signoff (Business)
  • Done 🚀

In practice we have been using a more simplified structure, essentially skipping the first 4 proposed columns above and starting from 'Ready for Dev':

  • Dependencies/Open Questions
  • Project backlog
  • Sprint backlog
  • In progress
  • Awaiting review
  • Awaiting testing
  • Done

Whilst this may seen simpler, in reality it means that more often than not, adding tech spec and time estimates just doesn't get done.

For internal dwyl projects and for our client projects, usually the PO is the final decision maker and provides sign off, so my only proposed modifications to this as a starting point would be:

  • Ideate: Define User Story / Project Backlog
  • Create UX/UI Wireframe/flow
  • Ready for Tech Spec (this is not something we currently add to anything other than very complex issues, we may need to provide some good examples)
  • Estimate time
  • Sprint backlog (things can only be moved here once they are time estimated)
    • Alternatively we use milestones only to demarcate sprint and this becomes the prioritised project back
  • In Development Progress (these can sometimes be questions
  • Ready for Awaiting Review
  • In Review (Pull Request)
    • We trialled this column in the CI project and it was never used, but my hypothesis is that this was because QAs don't go through the Projects, they look at what is assigned to them only - if adding the in-review label automagically moved the issue into this column, then we could keep the column
  • Ready for Test
  • In Test - Even our best POs have not in the past moved any issues in the Project. Unless there is a dedicated Tester, I would vote that we remove this column for simplification - the issue is either awaiting test, has a bug or a question or is 'done'
  • Ready for Signoff (Business) - I would also suggest we remove this column as for now, the vast majority of our issues go from Awaiting Testing to Done as the PO/tester also provides sign off
  • Done 🚀

I suggest we add a 'Dependencies/Open Questions' column to this list because it is useful for the dev team and POs to keep track of what's blocking work.

主要言語
言語のデータがありません
スター
91
フォーク
9
30日以内にマージされた PR はありません

環境構築

はじめの一歩

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

dwyl/contributing のほかの issue

dwyl/contributing の issue をすべて見る

似ている issue

DevTools の issue をもっと見る

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

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