Priorities: what should NG do that upstream doesn't? #5
SysAdminDoc
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
A fork only justifies its existence by making different choices, so I want to hear which choices actually matter to you.
Things already on my mind: staying ahead on new Android releases (there's Android 17 compat work happening now), trimming features that add attack surface without earning their keep, and keeping rootless workflows first class rather than treating root as the assumed baseline.
What's missing from your workflow? And the reverse question is just as useful: what does upstream do that NG should deliberately not do? I won't promise a queue position for anything, but everything posted here gets read, and the asks that keep recurring genuinely move up the list.
All reactions