XeplosionGames/.profile
1
1
Fork 0
Code Issues 2 Pull requests Projects 1 Releases Packages Wiki Activity Actions

Create a reusable project board template with standard columns #2

New issue
Closed
opened 2026-05-18 20:25:38 -06:00 by Xeplosion · 3 comments
Xeplosion commented 2026-05-18 20:25:38 -06:00
Owner
Copy link

Description

All new projects should follow a standard column structure. We need to document and enforce the following columns:

Column Color Purpose
Backlog Grey #6b7280 Ideas and future work
To Do Blue #3b82f6 Planned and ready to start
In Progress Amber #f59e0b Currently being worked on
Completed Green #22c55e Done

Acceptance Criteria

  • Standard columns are documented in CONVENTIONS.md.
  • All existing project boards are updated to match.
## Description All new projects should follow a standard column structure. We need to document and enforce the following columns: | Column | Color | Purpose | |---|---|---| | Backlog | Grey `#6b7280` | Ideas and future work | | To Do | Blue `#3b82f6` | Planned and ready to start | | In Progress | Amber `#f59e0b` | Currently being worked on | | Completed | Green `#22c55e` | Done | ## Acceptance Criteria - Standard columns are documented in `CONVENTIONS.md`. - All existing project boards are updated to match.
Xeplosion commented 2026-05-18 20:36:09 -06:00
Author
Owner
Copy link

It would be helpful to create a few example issues that demonstrate appropriate usage of each column, including what a properly formatted backlog item looks like vs a to do item that is ready to be worked on. This would give contributors a clear reference when adding new issues to any project board.

It would be helpful to create a few example issues that demonstrate appropriate usage of each column, including what a properly formatted backlog item looks like vs a to do item that is ready to be worked on. This would give contributors a clear reference when adding new issues to any project board.
Xeplosion commented 2026-05-18 20:36:28 -06:00
Author
Owner
Copy link

Created the Projects Template project board in the org repo as a reference implementation of the standard column structure. This can be used as a guide when setting up new project boards across the org.

Created the **Projects Template** project board in the `org` repo as a reference implementation of the standard column structure. This can be used as a guide when setting up new project boards across the org.
Xeplosion commented 2026-05-24 08:16:43 -06:00
Author
Owner
Copy link

Closing this issue and opening a new one that more closely follows the convetions recently described in the .forgejo repo.

Closing this issue and opening a new one that more closely follows the convetions recently described in the `.forgejo` repo.
Xeplosion added spent time 2026-05-24 08:46:29 -06:00
15 minutes
Sign in to join this conversation.
master
Branches Tags
Clear current reference
master
Clear current reference
No results found.
Labels
Clear labels   
Compat/Breaking
Breaking change that won't be backward compatible

  
Kind/Bug
Something is not working

  
Kind/Documentation
Documentation changes

  
Kind/Enhancement
Improve existing functionality

  
Kind/Feature
New functionality

  
Kind/Security
This is security issue

  
Kind/Testing
Issue or pull request related to testing

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Reviewed
Confirmed
 Issue has been confirmed

  
Reviewed
Duplicate
 This issue or pull request already exists

  
Reviewed
Invalid
 Invalid issue

  
Reviewed
Won't Fix
 This issue won't be fixed

  
Status
Abandoned
 Somebody has started to work on this but abandoned work

  
Status
Blocked
 Something is blocking this issue or pull request

  
Status
Need More Info
 Feedback is required to reproduce issue or to continue work

  
Compat/Breaking
Introduces a breaking change — not backward compatible

  
Compat/Deprecation
Deprecates something that will be removed in a future release

  
Kind
Bug
 Something is not working

  
Kind
Chore
 Maintenance, dependencies, tooling, tech debt

  
Kind
Documentation
 Documentation changes

  
Kind
Enhancement
 Improve existing functionality

  
Kind
Feature
 New functionality

  
Kind
Investigation
 Research or spike — output is findings, not necessarily a PR

  
Kind
Question
 Question or discussion — no code change intended

  
Kind
Security
 Security-related issue or fix

  
Kind
Testing
 Related to tests or test infrastructure

  
Meta/Good First Issue
Good entry point for new contributors

  
Meta/Help Wanted
Extra attention or outside help welcome

  
Meta/Stale
No activity for 60+ days — will be closed if no response

  
Priority
Critical
 Drop everything — production is broken or data is at risk

  
Priority
High
 Next up — significant impact, should ship soon

  
Priority
Low
 Nice to have — pick up when bandwidth allows

  
Priority
Medium
 Important but not blocking anything

  
Resolution
Confirmed
 Issue is valid and ready to be worked on

  
Resolution
Duplicate
 Already tracked in another issue

  
Resolution
Invalid
 Cannot reproduce, out of scope, or not a real issue

  
Resolution
Won't Fix
 Acknowledged but will not be addressed

  
Status
Abandoned
 Work was started but the contributor stepped away

  
Status
Blocked
 Cannot proceed — waiting on something external

  
Status
Needs More Info
 Waiting on additional information from the reporter

  
Status
Needs Triage
 Newly opened — awaiting review, kind, and priority assignment

No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Compat/Breaking
Compat/Deprecation
Kind
Bug
Kind
Chore
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Investigation
Kind
Question
Kind
Security
Kind
Testing
Meta/Good First Issue
Meta/Help Wanted
Meta/Stale
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Resolution
Confirmed
Resolution
Duplicate
Resolution
Invalid
Resolution
Won't Fix
Status
Abandoned
Status
Blocked
Status
Needs More Info
Status
Needs Triage
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Infrastructure & Devops
Assignees
Clear assignees
No assignees
1 participant
Notifications
Total time spent: 15 minutes
Xeplosion
15 minutes
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
XeplosionGames/.profile#2
No description provided.