- mobian-tweaks + device-specific packages refactoring
- a-wai working on it, expecting a prototype ready by the end of March:
- have all config files in a single /etc/mobile-tweaks folder
- run a service on first boot to identify the device type (based on DT compatible or DMI output) and copy/link the appropriate files
- extract firmware from android partitions on sdm845 devices
- a-wai working on it, expecting a prototype ready by the end of March:
image creation on salsa.d.o in the long term? https://salsa.debian.org/debian/grow-your-ideas/-/issues/27
- Device firmware (bootloader) for PP/PPP
- How to talk to users about the changes
- document in the wiki as a 1st step: install bootloader/firmware first, then flash the mobian image and enjoy
- will need a blog post when we get there (need a tow-boot official release first)
- How to talk to users about the changes
- moving to a unified (instead of per-processor) kernel
- challenges of "maintaining" 500-1k patches in a single tree
- QA will need to be thought of so we don't break a device while updating patches for another one
- Next steps towards Mobian as a Debian Blend
- gitlab/salsa split
- keep packages we host in our repo on gitlab, move to salsa as we get them into debian
- not an ideal solution, can confuse existing Debian maintainers/developers
- works well for the pine64 community as a lot is already on gitlab.com (pmOS, pine64-org...)
move repos from the salsa "Mobian-team" group to either the "debian" or "?DebianOnMobile-team" group
- keep packages we host in our repo on gitlab, move to salsa as we get them into debian
- wiki split: wiki.mobian-project.org / gitlab / wiki.debian.org
- gitlab wiki to be moved to wiki.debian.org (federico)
- wiki.mobian.org is easier/less intimidating for users to contribute to, let's keep it that way for now
- mobian.debian.net usage?
federico to setup mobile.debian.net & mobian.debian.net to redirect to our home page.
- upstreaming process status and remaining work
- packages which could be uploaded to Debian:
- firefox-esr-mobile-config
- eg25-manager
- calamares-extensions
- postmarketos-tweaks (could maybe be renamed?)
- pd-mapper
- rmtfs
- qrtr
- tqftpserv
- Mobian packages to upload to Debian:
- mobian-plymouth-theme (maybe rename to "plymouth-theme-mobian" for consistency)
- meta-mobian (needs to be reworked, best to wait for the mobian-tweaks/mobile-tweaks refactor and merge)
- calamares-settings-mobian (needs calamares-extensions first)
- Debian native packages we need to upstream patches to:
- u-boot-menu
- devrtz to check with Jonas if current MRs should be converted to BTS patches
- zram-tools: introduce a max size, 50% of RAM is good on PP, a bit too much on OP6 w/6-8G RAM (and actually doesn't work)
- current version seems to default to 50% but not in the repo yet
maybe switch to https://github.com/systemd/zram-generator instead ?
- u-boot-menu
- packages which could be uploaded to Debian:
- gitlab/salsa split
Maintaining kernel packages is time-consuming and often straightforward (when rebasing on stable releases) => look at ways of automating this process
- Possible workflow for adding patches:
- "patches" branch for reference (target for MRs)
Upon merging, have CI pick commits from the patches branch and turn those into quilt patches for the mobian-$KVER branch
CI creates MR against mobian-$KVER for including new patches
- Rebasing on minor releases is easier, can be done with a daily CI job:
- Fetch latest tags from stable kernel repo
If tag > current base version then rebase on latest upstream tag
- If no conflict, create MR
- Else, create issue
Partial implementation: https://gitlab.com/undef1/Snippets/-/snippets/2265951
- Undef to experiment with this
- Possible workflow for adding patches:
- Meeting time. Does this still work for everyone? Spaetz seems permanently unable to make it.
- Run a new poll to check again what's best
- Modem firmware licensing and updates?
- Not our problem, we don't host/distribute it
