Skip to content

Conversation

@jhagberg
Copy link
Contributor

Add GitHub Issue Templates and Labels

Summary

This PR adds GitHub integration to make it easy for people to ask architecture questions:

  • Issue template for architecture-question
  • Configuration for additional contact links
  • Proposed label structure for workflow management

Proposed Labels

I suggest we create these labels manually after merging:

Core Labels (Required)

Label Color Description Usage
architecture-question #0E8A16 (green) Questions for the architecture board Auto-applied by template
high-impact #D93F0B (red) Affects all platforms Requester or board adds
urgent #B60205 (dark red) Needs response within 48 hours Requester adds (sparingly)
adr-needed #5319E7 (purple) Should be documented as ADR Board adds during discussion

Optional Status Labels

Label Color Description Usage
needs-decision #FBCA04 (yellow) Discussion ongoing, decision pending Board workflow
waiting-for-feedback #FEF2C0 (light yellow) Waiting for requester response Board workflow
resolved #0E8A16 (green) Question answered Board closes issue

Optional Category Labels

Label Color Description
integration #1D76DB (blue) Integration between systems
standards #1D76DB (blue) Standards and specifications
security #D93F0B (red) Security-related
infrastructure #BFD4F2 (light blue) Hardware/storage/compute

Discussion question: Should we start with just the 4 core labels and add more as needed? Or create the full set upfront?

Blank Issues: Enabled ✅

Set to true to lower barrier. Anyone can open issue without template.

Rationale: Better to be welcoming than strict. We can require templates later if needed.

Question: Agree, or should we require template usage?

Discussion Questions for Reviewers

  1. Label set: Start with 4 core labels or create all 11 upfront?
  2. Blank issues: Keep enabled (true) or require template (false)?
  3. Template tone: Too casual? Too formal? Just right?
  4. Template fields: Missing anything important? Too many fields?
  5. Contact links: Should we add Slack channel if we create one?

@jhagberg jhagberg requested a review from a team November 26, 2025 11:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants