Skip to content

Commit

Permalink
Add a Phase 0 issue template to use when engineering input into new h…
Browse files Browse the repository at this point in the history
…ub refinement is required
  • Loading branch information
sgibson91 committed Oct 2, 2024
1 parent ecb3340 commit 86d22e1
Showing 1 changed file with 31 additions and 0 deletions.
31 changes: 31 additions & 0 deletions .github/ISSUE_TEMPLATE/02_new-hub_phase-0.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
name: "New Hub Turnup Phase 0 - Partnership/Engineering sync chat"
description: |
If partnerships need a conversation with an engineer to help with filling out
the other phases, they should open this type of issue to trigger that process.
title: "[New Hub] [Spike: 30mins] Sync chat to refine phases - {{community_name}}"
projects: ["2i2c-org/49"]
body:
- type: markdown
attributes:
value: |
This issue is to be used when Partnerships require some engineering assistance
to refine the requirements for an upcoming new hub deployment.
### Tasks
```[tasklist]
- [ ] Schedule a 30min sync chat with James Munroe, or a delegate, to refine the new hub requirements
- [ ] Refine the requirements for this new hub deployment
- [ ] Open the relevant Phase 1,2,3 issues with all of the required information
```
### Definition of Done
Each of the following phases for this new hub deployment:
- have an open issue,
- all the relevant information in the issue tables are filled out and marked READY,
- the issues have been placed in the Refined column of the Engineering board
- [ ] Phase 1
- [ ] Phase 2
- [ ] Phase 3

0 comments on commit 86d22e1

Please sign in to comment.