Files

T

Tirsvad 424f14f4f5 Plan RepoFoundry: business case, stakeholders, plan, milestones, UC-001

Add the planning baseline for RepoFoundry (create-project.sh), which
creates GitHub and Gitea repositories, a Gitea -> GitHub push mirror and
a local project with the SQA-QC-Framework.

- BC-001 Business Case and SA-001 Stakeholder Analysis (S01, S02, S03)
- PP-001 Project Plan: three phases, 2026-10-05 to 2026-11-13 (proposed)
- MIL-001 Foundation, MIL-002 Repositories and Mirror,
  MIL-003 Scaffold and Release, with 18 task rows
- US-001, UC-001 "Create a new project" and SSD-001
- Registry: PO language en; PP, MIL, US, UC and SSD rows added

Decisions recorded: origin uses HTTPS from GITEA_URL unless the SSH test
on port 10022 passes; S01 and S02 are held by one person for now.

Refs: no issues synced yet (sync-project.sh dry run only)

2026-10-05 12:30:29 +08:00

3.2 KiB

Raw Blame History

Stakeholder Analysis

Metadata

Key	Value
ID	SA-001
CrossReference	BC-001

Version History

Date	Status	Author	Reviewer	Change	Commit
2026-10-05	Proposed	Jens Tirsvad Nielsen	S02	Initial version	9ae0cba

Purpose

Identify who is affected by RepoFoundry and what each needs from it, so owners and reviewers in later artifacts can cite stable IDs. Method: power/interest grid.

Stakeholder Summary Table

ID	Name	Role/Title	Organization	Power Level	Interest Level	Quadrant	Primary Concern (Business Language)
S01	Tirsvad	Product Owner and maintainer	Not stated	HIGH	HIGH	Manage Closely	New projects start from one repeatable, correct setup
S02	Michael Kragh	DevOps, cybersecurity and maintainer	Not stated	HIGH	HIGH	Manage Closely	Credentials are never exposed and the git host integration is safe
S03	GitHub readers	Readers of the published project	Not stated	LOW	MEDIUM	Keep Informed	Clear documentation they can follow and reuse

Power/Interest Classification Rationale

Manage Closely (S01, S02): the two maintainers decide scope, accept the result and own the code. For now one person holds both roles, so one person both authors and reviews; this should be revisited when a second person takes S02.
Keep Informed (S03): readers cannot change the project but depend on its README being accurate.

Primary Concerns and FURPS+ Mapping

ID	Concern	FURPS+ attribute
S01	One command creates both repositories, the mirror and the project	Functionality
S02	No token in output, URLs or files; no silent overwrite	Functionality (security)
S02	A failed step leaves a clear record of what exists	Reliability
S03	Installation, configuration and usage are documented in clear English	Usability

Communication Requirements

ID	Channel	Frequency	Deliverable	Phase / Milestone
S01	Pull request review	Per phase	Accepted milestone document	MIL-001, MIL-002, MIL-003
S02	Pull request review	Per phase	Security review of the changes	MIL-002, MIL-003
S03	README on GitHub	At release	README.md	MIL-003

Conflicting Interests and Mitigations

Conflict	Stakeholders	Mitigation
Convenience of one-step setup against strict consent prompts for every overwrite	S01, S02	Prompt only where something would be changed; offer `--yes` only for non-destructive steps (to be decided in MIL-001)

Traceability Analysis

Business Goal Alignment

Stakeholder	Concern	Business Case objective
S01	One-command setup	BC-001 objectives 1–5
S02	Credential safety, no overwrite	BC-001 objective 6
S03	Reusable documentation	BC-001 objective 6 and the README deliverable

Sign-Off

Pending review by S02.

3.2 KiB Raw Blame History Unescape Escape