vasilito/RedBear-OS
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: retire GitHub contribution language

Browse Source
This commit is contained in:
Vasilito
2026-05-09 01:38:03 +01:00
parent a6d3e85588
commit ae7b5f989f
2 changed files with 22 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+7 -2
View File
@@ -6,10 +6,15 @@ When a commit changes the visible system surface, supported hardware, build flow
or major documentation status, add a short note here and keep the README "What's New" section in or major documentation status, add a short note here and keep the README "What's New" section in
sync with the newest highlights. sync with the newest highlights.
## 2026-05-09 — Repository Hosting
- Documented Gitea as the only canonical Red Bear OS Git server and explicitly retired GitHub as a
Red Bear code, issue, release, or coordination target.
## 2026-04-14 ## 2026-04-14
- Added a canonical GitHub-visible Red Bear OS implementation plan under `docs/` and linked it from the main README and docs index. - Added a canonical Gitea-visible Red Bear OS implementation plan under `docs/` and linked it from the main README and docs index.
- Added a user-visible GitHub-facing "What's New" section to the root README and linked it to this running changelog. - Added a user-visible Gitea-facing "What's New" section to the root README and linked it to this running changelog.
- Added a new `redbear-kde` configuration and documented current KDE bring-up status as in-progress rather than not started. - Added a new `redbear-kde` configuration and documented current KDE bring-up status as in-progress rather than not started.
- Refreshed top-level and docs status notes so historical roadmap documents no longer read as the current repo state. - Refreshed top-level and docs status notes so historical roadmap documents no longer read as the current repo state.
- Expanded shipped Red Bear system tooling and config coverage around runtime diagnostics, native hardware listing, and Redox-native networking flows. - Expanded shipped Red Bear system tooling and config coverage around runtime diagnostics, native hardware listing, and Redox-native networking flows.
CONTRIBUTING.md
+15 -2
View File
@@ -130,13 +130,26 @@ Since **Rust** is a relatively small and new language compared to others like C
Please follow our [Git style](https://doc.redox-os.org/book/creating-proper-pull-requests.html) for pull requests. Please follow our [Git style](https://doc.redox-os.org/book/creating-proper-pull-requests.html) for pull requests.
For user-visible work, keep the root [`CHANGELOG.md`](CHANGELOG.md) current and immutable archived the For user-visible work, keep the root [`CHANGELOG.md`](CHANGELOG.md) current and immutable archived the
README "What's New" section with the latest highlights so GitHub visitors can immediately see what README "What's New" section with the latest highlights so Gitea visitors can immediately see what
changed. changed.
When a commit changes the visible system surface, supported hardware, build flow, shipped configs, When a commit changes the visible system surface, supported hardware, build flow, shipped configs,
or key docs, add a short user-facing changelog note in the same change. or key docs, add a short user-facing changelog note in the same change.
## GitLab ## Red Bear Git Hosting
The canonical Red Bear OS Git server is **Gitea**:
```text
https://gitea.redbearos.org/vasilito/RedBear-OS.git
```
Do not push Red Bear OS work to GitHub. GitHub is not a Red Bear source of truth for code,
issues, releases, or project coordination. Upstream Redox references may still point to GitLab or
other upstream project hosts where historically appropriate, but Red Bear-owned development and
review happen on Gitea.
## Upstream Redox GitLab
### Identity ### Identity