zgaetano/datarhei-dragonfork-core
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases 4 Packages Wiki Activity Actions

M5: Dragon Fork branding + v0.1.0-dragonfork #10

Closed
zgaetano wants to merge 0 commits from m5-branding-release into m2-webrtc-core-integration
pull from: m5-branding-release
merge into: zgaetano:m2-webrtc-core-integration
Conversation 1 Commits - Files changed -
zgaetano commented 2026-05-03 08:22:42 -04:00
Owner
Copy link

Last milestone: project identity + first tagged release.

Identity

  • app/version.go gains Variant ("dragonfork") and Fork ("Datarhei — Dragon Fork") as vars — overridable via -ldflags for downstream re-packagers.
  • api.About + the /api endpoint now expose variant and fork fields; Swagger docs regenerated.
  • Startup banner logs variant + fork alongside the existing application + version fields, so tail-following /var/log makes the fork unmistakable at a glance.
  • Module path stays github.com/datarhei/core/v16 by design — the fork is distinguished by repo location + branch history, not import path. (Documented in NOTES.md since M1 baseline.)

Documentation

  • README.md rewritten — Dragon Fork header, sample process JSON, multi-input pipeline guidance, links to the design and testing docs. Upstream feature surface summarised under "From upstream Datarhei" with an explicit additivity statement.
  • NOTICE — Apache 2.0 §4(d) attribution (upstream Datarhei Core, Pion, Echo, FFmpeg).
  • CREDITS — enumerated dependency list with licenses.
  • CHANGELOG.md prepended with a "Datarhei — Dragon Fork" section starting at v0.1.0-dragonfork; upstream's # Core history preserved below.

Release

After this lands on main (post-merge of M2 + M3 + M4 + M5), tag v0.1.0-dragonfork and create a Forgejo Release pointing at the same commit.

Files

NOTICE                    |  41 +++
CREDITS                   |  47 +++
README.md                 | rewritten
CHANGELOG.md              | Dragon Fork section prepended
app/version.go            | +Variant, +Fork
app/api/api.go            | banner additions
http/api/about.go         | +Variant, +Fork DTO fields
http/handler/api/about.go | populate the new fields
docs/docs.go|.json|.yaml  | swagger regenerated

Stack

Targets m2-webrtc-core-integration so it lands without depending on M3/M4 PRs. The branding is independent of the WebRTC robustness and CI work; the merge order can be M2 → M3 → M4 → M5 or any other sequence the reviewer prefers.

Co-authored with Claude Opus 4.7.

Last milestone: project identity + first tagged release. ## Identity - **`app/version.go`** gains `Variant` (`"dragonfork"`) and `Fork` (`"Datarhei — Dragon Fork"`) as `var`s — overridable via `-ldflags` for downstream re-packagers. - **`api.About`** + the `/api` endpoint now expose `variant` and `fork` fields; Swagger docs regenerated. - **Startup banner** logs `variant` + `fork` alongside the existing `application` + `version` fields, so tail-following `/var/log` makes the fork unmistakable at a glance. - **Module path stays `github.com/datarhei/core/v16`** by design — the fork is distinguished by repo location + branch history, not import path. (Documented in `NOTES.md` since M1 baseline.) ## Documentation - **`README.md`** rewritten — Dragon Fork header, sample process JSON, multi-input pipeline guidance, links to the design and testing docs. Upstream feature surface summarised under "From upstream Datarhei" with an explicit additivity statement. - **`NOTICE`** — Apache 2.0 §4(d) attribution (upstream Datarhei Core, Pion, Echo, FFmpeg). - **`CREDITS`** — enumerated dependency list with licenses. - **`CHANGELOG.md`** prepended with a "Datarhei — Dragon Fork" section starting at `v0.1.0-dragonfork`; upstream's `# Core` history preserved below. ## Release After this lands on `main` (post-merge of M2 + M3 + M4 + M5), tag `v0.1.0-dragonfork` and create a Forgejo Release pointing at the same commit. ## Files ``` NOTICE | 41 +++ CREDITS | 47 +++ README.md | rewritten CHANGELOG.md | Dragon Fork section prepended app/version.go | +Variant, +Fork app/api/api.go | banner additions http/api/about.go | +Variant, +Fork DTO fields http/handler/api/about.go | populate the new fields docs/docs.go|.json|.yaml | swagger regenerated ``` ## Stack Targets `m2-webrtc-core-integration` so it lands without depending on M3/M4 PRs. The branding is independent of the WebRTC robustness and CI work; the merge order can be M2 → M3 → M4 → M5 or any other sequence the reviewer prefers. Co-authored with Claude Opus 4.7.
zgaetano added 1 commit 2026-05-03 08:22:42 -04:00
feat(branding): Dragon Fork identity for v0.1.0-dragonfork release
Some checks failed
tests / build (push) Failing after 2s
Details
tests / build (pull_request) Failing after 2s
Details
671f64ca56 
M5 / final M2-stack work. The fork now identifies itself unambiguously
in logs, the API, and the README without changing the Go module path
(internal imports stay at github.com/datarhei/core/v16 — see NOTES.md
for the rationale).

Identity surfaces:

- app/version.go gains Variant ('dragonfork') and Fork ('Datarhei —
  Dragon Fork') as vars (overridable via -ldflags for downstream
  re-packagers).
- api.About + the /api endpoint expose 'variant' and 'fork' fields;
  Swagger docs regenerated.
- Startup banner logs 'variant' + 'fork' alongside the existing
  application + version fields, so a TrueNAS sysadmin tail-following
  /var/log can tell at a glance which fork is running.

Documentation:

- README.md rewritten with a Dragon Fork header and Quick start; the
  upstream feature surface is summarised in 'From upstream Datarhei'
  with a clear additivity statement. Sample process JSON, multi-input
  pipeline guidance, link to the design + testing docs.
- NOTICE: Apache 2.0 §4(d) attribution to upstream datarhei Core,
  Pion, Echo, FFmpeg.
- CREDITS: enumerated dependency list with licenses.
- CHANGELOG.md prepended with a 'Datarhei — Dragon Fork' section
  starting at v0.1.0-dragonfork; upstream's '# Core' history preserved
  below.

Module path stays github.com/datarhei/core/v16 by design — the fork is
distinguished by repo location and branch history, not import path.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
zgaetano commented 2026-05-03 08:28:58 -04:00
Author
Owner
Copy link

Merged into main via direct push as part of the v0.1.0-dragonfork release. Branch commits are reachable from main; closing this PR. Release: https://forge.wilddragon.net/zgaetano/datarhei-dragonfork-core/releases/tag/v0.1.0-dragonfork

Merged into `main` via direct push as part of the v0.1.0-dragonfork release. Branch commits are reachable from main; closing this PR. Release: https://forge.wilddragon.net/zgaetano/datarhei-dragonfork-core/releases/tag/v0.1.0-dragonfork
zgaetano closed this pull request 2026-05-03 08:28:58 -04:00
Some checks failed
tests / build (push) Failing after 2s
Details
tests / build (pull_request) Failing after 2s
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: zgaetano/datarhei-dragonfork-core#10
No description provided.
Delete branch "m5-branding-release"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?