docs: bootstrap AtayMakhzan fork identity
Co-Authored-By: Al-Khawarizmi <al-khawarizmi@hermes.local>
This commit is contained in:
@@ -0,0 +1,57 @@
|
||||
# AtayMakhzan
|
||||
|
||||
AtayMakhzan is Saad ibn Zoubayr's sovereign Moroccan developer forge.
|
||||
|
||||
This repository is an intentional source fork of upstream Gitea. The goal is not to create a cosmetic copy. The goal is to build a controlled forge system for Saad's ventures while preserving upstream security and maintainability discipline.
|
||||
|
||||
## Upstream basis
|
||||
|
||||
Initial fork basis:
|
||||
|
||||
```text
|
||||
Gitea v1.26.2
|
||||
```
|
||||
|
||||
Upstream remote:
|
||||
|
||||
```text
|
||||
https://github.com/go-gitea/gitea.git
|
||||
```
|
||||
|
||||
AtayMakhzan origin:
|
||||
|
||||
```text
|
||||
ssh://git@ataymakhzan.com:2222/ibnezzoubayr/Atay-Makhzan.git
|
||||
```
|
||||
|
||||
## Product doctrine
|
||||
|
||||
AtayMakhzan should be:
|
||||
|
||||
- sovereign: code, repos, and infra controlled by Saad;
|
||||
- Moroccan: tasteful identity, not decorative folklore;
|
||||
- developer-first: fast, calm, reliable, and sharp;
|
||||
- operations-safe: backups and rollback before production changes;
|
||||
- upstream-aware: security releases are merged deliberately.
|
||||
|
||||
## Fork discipline
|
||||
|
||||
- Preserve upstream MIT license and copyright notices.
|
||||
- Track upstream releases and security patches.
|
||||
- Document every divergence in `FORK_CHANGELOG.md`.
|
||||
- Add tests for behavioral changes.
|
||||
- Avoid schema/auth/storage changes until a migration and rollback plan exists.
|
||||
- Keep production deploy logic in `Atay-Makhzan-Ops`, not in this source repo.
|
||||
|
||||
## First milestone
|
||||
|
||||
The first milestone is a buildable, deployable fork that behaves like Gitea 1.26.2 with safe AtayMakhzan identity changes only.
|
||||
|
||||
Non-goals for the first milestone:
|
||||
|
||||
- no database schema change;
|
||||
- no authentication rewrite;
|
||||
- no SSH/Git transport change;
|
||||
- no permission model change;
|
||||
- no broad UI rewrite;
|
||||
- no production deployment until staging/smoke verification passes.
|
||||
Reference in New Issue
Block a user