docs: rebrand to nexterUI and document why this fork exists - #3
Open
lepht wants to merge 2 commits into
Open
Conversation
This was referenced Aug 8, 2026
lepht
pushed a commit
that referenced
this pull request
Aug 9, 2026
Follows the rebrand in #3 so the pak docs don't stay on the old name once it merges. Renames references to this OS and its behavior, and keeps "NextUI" for the four places it is still the correct name: - a compatibility note up top: nexterUI keeps the pak format unchanged, so paks built for NextUI work here as-is and this document applies to both - IS_NEXT is set by both nexterUI and NextUI, so it detects the lineage rather than the fork; nothing in the environment separates the two - the third-party support caveat, which is true of upstream and MinUI too Also replaced a "NextUI-only features" code comment with "not available on stock MinUI", which is what the IS_NEXT guard actually means. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Hu2BibaMPDtFk7S3NYywZE
This was referenced Aug 11, 2026
lepht
force-pushed
the
docs/rebrand-nexterui
branch
from
August 11, 2026 21:57
d0a719e to
a55f109
Compare
lepht
force-pushed
the
docs/rebrand-nexterui
branch
from
August 11, 2026 22:20
a55f109 to
a4d87d2
Compare
lepht
force-pushed
the
docs/rebrand-nexterui
branch
from
August 11, 2026 22:43
a4d87d2 to
f90149b
Compare
lepht
force-pushed
the
docs/rebrand-nexterui
branch
from
August 12, 2026 00:41
f90149b to
9fc29ba
Compare
lepht
force-pushed
the
docs/rebrand-nexterui
branch
from
August 12, 2026 01:25
9fc29ba to
5437338
Compare
lepht
force-pushed
the
docs/rebrand-nexterui
branch
from
August 12, 2026 03:42
5437338 to
85dfe5d
Compare
Cosmetic rebrand only: README, the on-card README and palette docs, and the Bluetooth advertised name. No binaries, paths or settings filenames are renamed, so nothing in the boot chain changes and existing cards keep working. Adds a "Why this fork" section covering the three reasons it exists - staying on an open licence as upstream moves to PolyForm Noncommercial, adding the conveniences upstream left to third-party paks, and clearing out inherited defects - while keeping attribution to NextUI and MinUI intact. Deliberately left alone, tracked as issues instead: - nextui.elf and the other internal identifiers - the boot logos and the missing header logo asset - MinUI.pak / MinUI.zip / minuisettings.txt / .minui, which existing installs depend on and which cannot be renamed without a migration
lepht
force-pushed
the
docs/rebrand-nexterui
branch
from
August 12, 2026 05:04
85dfe5d to
083839b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cosmetic rebrand to nexterUI, plus the "Why this fork" section.
What changed
README.md— name, badges and links point here rather than upstream; new Why this fork sectionskeleton/BASE/README.txt— the README shipped on the cardskeleton/BASE/Palettes/README.txt"$TRIMUI_MODEL (NextUI)"→(nexterUI), both platformslepht/nexterUI)The rationale section states the three reasons plainly: staying on an open licence as upstream moves to PolyForm Noncommercial, adding the conveniences upstream left to third-party paks (OS-level favorites and search, more in the spirit of OnionOS), and clearing out inherited defects. Attribution to NextUI and MinUI is kept — most of this code is theirs, and the GPL requires it.
What was deliberately not renamed
Nothing load-bearing. No binaries, paths, settings filenames or struct names, so the boot chain is untouched and existing cards keep working. Tracked as follow-up issues instead:
nextui.elf,/tmp/nextui_exec, the log filename andNextUISettings— a contained rename, but it runs through each platform'sMinUI.pak/launch.sh, and I can't verify a boot on hardware from here (Rebrand: rename internal identifiers (nextui.elf and friends) #4)MinUI.pak/MinUI.zip/minuisettings.txt/.userdata/shared/.minui/— these should not be renamed at all without a migration step. They're MinUI heritage rather than NextUI branding, and renaming them orphans every existing user's settings, saves, recents and favorites, and breaks the updater.Incidental fix
The old header referenced
github/logo_outline.png, which isn't in the repo — the image was broken on the rendered README. Replaced with a text heading until there's real artwork (#5).Verification
No code changes. Both
bt_init.shfiles passsh -n, and I confirmed by diff that nonextui.elf/nextui_exec/minuisettings/.minui/NextUISettingsreference was touched.