XeplosionTechnologies/.forgejo

Watch

Fork 0

Build Xeplosion Technologies workflow and standards Wiki #29

New issue

Open

opened 2026-09-07 17:33:59 +00:00 by Xeplosion · 0 comments

Xeplosion commented

2026-09-07 17:33:59 +00:00

Owner

Where is the problem?

Xeplosion Technologies .forgejo Wiki:

https://git.xetech.online/XeplosionTechnologies/.forgejo/wiki/

Type of documentation issue

Missing — the topic is not documented

What should change?

Build the initial contributor-facing Wiki for Xeplosion Technologies work-management and development standards.

This issue governs the overall Wiki effort. Individual page issues may be created and linked here as work begins.

Initial pages:

Home
Issues
Labels
Project Boards
Workflow Lifecycle
Git
Commits
Testing
Technical Debt
CI/CD
.NET & MonoGame
Node
TypeScript
Python
PHP
Shell & Scripts
Google Sheets
New Organization

The Wiki should be useful to any contributor, not only developers.

Issues may represent:

product or code work;
bugs and enhancements;
documentation;
investigations;
infrastructure;
data work;
configuration;
research;
questions;
other trackable organizational work.

Work that does not directly involve code or the functionality of a code-based product should generally use an appropriate separate project board instead of being mixed into a product-development board.

The Home page should briefly introduce:

Triage → Backlog → To Do → In Progress → [In Review] → Completed

and explain why a common lifecycle allows contributors with different technical backgrounds to coordinate work.

The dedicated Workflow Lifecycle page should document the mechanics of each stage.

Use the canonical lifecycle project board and the standardized Example #1 through Example #6 naming for the lifecycle example issues.

Source of truth / validation

README.md
WORKFLOW.md
ISSUES.md
LABELS.md
PULL_REQUESTS.md
canonical project board:
https://git.xetech.online/XeplosionTechnologies/.forgejo/projects/4
canonical templates and automation maintained on .forgejo main

Additional context

The page hierarchy may evolve later. This issue establishes the initial baseline and provides one governing issue under which page-specific work can be tracked.

Request checklist

I identified the documentation location or clearly described where the new documentation belongs
I described the intended corrected or improved content

Workflow lifecycle

Triage

Kind/ classification confirmed
Issue validity reviewed and appropriate Reviewed/ label assigned
Priority/ assigned when appropriate
Applicable Branch/ label(s) assigned when branch targeting matters
Information requirements resolved; no Status/Needs More Info remains
Status/Needs Triage removed before leaving Triage

Backlog

Issue is confirmed valid and accepted into the project backlog

To Do

Scope and expected outcome are sufficiently defined
Known prerequisites, dependencies, and required decisions are resolved or understood
Work has been deliberately selected as upcoming work

In Progress

Assignee or active owner identified when appropriate
Forgejo timer started when time tracking provides meaningful value
Relevant implementation, research, or work notes recorded as needed
Forgejo timer stopped when active work ends, pauses, or becomes blocked

Review Gate

Review requirement assessed based on complexity, criticality, reversibility, and impact
If review is required: moved to In Review and appropriate testing / validation performed
If review is required: review comment records what was reviewed, how it was validated, findings, and outcome
If review is not required: rationale is evident from the low-risk nature of the change

Completed

Acceptance criteria / intended outcome satisfied
Related PRs, commits, documentation, or external changes linked where applicable
Final resolution comment explains what changed, how the issue was resolved, and how it was verified
Follow-up work split into separate issues where appropriate
Any Forgejo timer is stopped and recorded time is final
Issue moved to Completed and closed

### Where is the problem? Xeplosion Technologies `.forgejo` Wiki: `https://git.xetech.online/XeplosionTechnologies/.forgejo/wiki/` ### Type of documentation issue Missing — the topic is not documented ### What should change? Build the initial contributor-facing Wiki for Xeplosion Technologies work-management and development standards. This issue governs the overall Wiki effort. Individual page issues may be created and linked here as work begins. Initial pages: * [ ] Home * [ ] Issues * [ ] Labels * [ ] Project Boards * [ ] Workflow Lifecycle * [ ] Git * [ ] Commits * [ ] Testing * [ ] Technical Debt * [ ] CI/CD * [ ] .NET & MonoGame * [ ] Node * [ ] TypeScript * [ ] Python * [ ] PHP * [ ] Shell & Scripts * [ ] Google Sheets * [ ] New Organization The Wiki should be useful to **any contributor**, not only developers. Issues may represent: * product or code work; * bugs and enhancements; * documentation; * investigations; * infrastructure; * data work; * configuration; * research; * questions; * other trackable organizational work. Work that does not directly involve code or the functionality of a code-based product should generally use an appropriate separate project board instead of being mixed into a product-development board. The Home page should briefly introduce: ```text Triage → Backlog → To Do → In Progress → [In Review] → Completed ``` and explain why a common lifecycle allows contributors with different technical backgrounds to coordinate work. The dedicated **Workflow Lifecycle** page should document the mechanics of each stage. Use the canonical lifecycle project board and the standardized **Example #1** through **Example #6** naming for the lifecycle example issues. ### Source of truth / validation * `README.md` * `WORKFLOW.md` * `ISSUES.md` * `LABELS.md` * `PULL_REQUESTS.md` * canonical project board: `https://git.xetech.online/XeplosionTechnologies/.forgejo/projects/4` * canonical templates and automation maintained on `.forgejo` `main` ### Additional context The page hierarchy may evolve later. This issue establishes the initial baseline and provides one governing issue under which page-specific work can be tracked. ### Request checklist - [x] I identified the documentation location or clearly described where the new documentation belongs - [x] I described the intended corrected or improved content ### Workflow lifecycle ### Triage - [x] `Kind/` classification confirmed - [x] Issue validity reviewed and appropriate `Reviewed/` label assigned - [x] `Priority/` assigned when appropriate - [x] Applicable `Branch/` label(s) assigned when branch targeting matters - [x] Information requirements resolved; no `Status/Needs More Info` remains - [x] `Status/Needs Triage` removed before leaving Triage ### Backlog - [x] Issue is confirmed valid and accepted into the project backlog ### To Do - [x] Scope and expected outcome are sufficiently defined - [x] Known prerequisites, dependencies, and required decisions are resolved or understood - [x] Work has been deliberately selected as upcoming work ### In Progress - [ ] Assignee or active owner identified when appropriate - [ ] Forgejo timer started when time tracking provides meaningful value - [ ] Relevant implementation, research, or work notes recorded as needed - [ ] Forgejo timer stopped when active work ends, pauses, or becomes blocked ### Review Gate - [ ] Review requirement assessed based on complexity, criticality, reversibility, and impact - [ ] If review is required: moved to **In Review** and appropriate testing / validation performed - [ ] If review is required: review comment records what was reviewed, how it was validated, findings, and outcome - [ ] If review is not required: rationale is evident from the low-risk nature of the change ### Completed - [ ] Acceptance criteria / intended outcome satisfied - [ ] Related PRs, commits, documentation, or external changes linked where applicable - [ ] Final resolution comment explains what changed, how the issue was resolved, and how it was verified - [ ] Follow-up work split into separate issues where appropriate - [ ] Any Forgejo timer is stopped and recorded time is final - [ ] Issue moved to **Completed** and closed

Xeplosion added the

labels

2026-09-07 17:33:59 +00:00

Xeplosion added this to the Forgejo Standards & Documentation project

2026-09-07 17:34:00 +00:00

Xeplosion self-assigned this

2026-09-07 17:35:31 +00:00

Xeplosion added reference docs