Skip to content
This repository was archived by the owner on Oct 10, 2025. It is now read-only.

Commit d96c010

Browse files
committed
docs: [#31] clarify repository transition strategy
- Add clear repository transition plan in docs/redesign/README.md - Current repo becomes 'torrust-tracker-demo-poc' (archived) - New repo 'torrust-tracker-installer' for implementation - Documentation transfer after Phase 4 completion - Separate specification (Phases 0-4) from implementation (Phases 5-7) - Update phase flow to show 8-phase complete process
1 parent ec4a2dd commit d96c010

File tree

1 file changed

+39
-1
lines changed

1 file changed

+39
-1
lines changed

docs/redesign/README.md

Lines changed: 39 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,36 @@
66
These docs (Issue **#31**) explain where we are going and why. Keep it light, clear and
77
useful for future contributors.
88

9+
## 🔄 Repository Transition Strategy
10+
11+
This repository serves as the **specification and design phase** for the new production
12+
system. Here's the complete transition plan:
13+
14+
### 1. **Current Repository (`torrust-tracker-demo`)**
15+
16+
- **Final Status**: Will be archived as `torrust-tracker-demo-poc`
17+
- **Purpose**: Historical reference and complete specification for new system
18+
- **Contains**: Complete documentation through Phase 4 (Goals → Requirements → Analysis → Design → Planning)
19+
- **Role**: Blueprint and specification source for the new implementation
20+
21+
### 2. **New Repository (`torrust-tracker-installer`)**
22+
23+
- **Purpose**: Production-grade deployment system implementation
24+
- **Foundation**: Copy of this redesign documentation as starting point
25+
- **Implementation Phases**:
26+
- **Phase 5**: Implementation 🔨
27+
- **Phase 6**: Testing & Validation 🧪
28+
- **Phase 7**: Migration & Deployment 🚀
29+
30+
### 3. **Documentation Handover**
31+
32+
- **What Transfers**: All `docs/redesign/` content copied to new repository
33+
- **What Stays**: PoC code and configuration (for historical reference)
34+
- **Timing**: After Phase 4 (Planning) completion in this repository
35+
36+
This approach separates **specification** (this repo) from **implementation** (new repo),
37+
ensuring clean separation of concerns and clear project boundaries.
38+
939
## What You Can Do Now
1040

1141
| You want to… | Allowed? | How |
@@ -38,14 +68,22 @@ After a quick review we move to Phase 2 (measure current behaviour: performance,
3868
| `phase4-planning/` | Milestones & rollout plan |
3969
| `community-input/` | Collected suggestions & feedback |
4070

41-
## Simple 5-Phase Flow
71+
## Simple 8-Phase Flow
72+
73+
**Specification & Design Phases** (in this repository):
4274

4375
0. Goals & scope (what we're trying to achieve)
4476
1. Requirements (what matters technically)
4577
2. Analyse current PoC (truth vs assumptions)
4678
3. Design new solution
4779
4. Plan build & migration
4880

81+
**Implementation Phases** (in new `torrust-tracker-installer` repository):
82+
83+
5. Implementation (build the new system)
84+
6. Testing & validation (comprehensive testing)
85+
7. Migration & deployment (production rollout)
86+
4987
## Next Up (Short List)
5088

5189
| Item | Phase | Status |

0 commit comments

Comments
 (0)