* move to salsa => complete * u-boot-menu (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012333) Status: awaiting review * look for a way to add "vccq mod" boot menu entry for OG PP and automatically detect it while installing the bootloader from the installer image => @Alex to look into it Q: Progress? * MR for pinephone-tweaks adding the vccq support package: https://salsa.debian.org/Mobian-team/devices/pinephone-tweaks/-/merge_requests/6 * MR for Calamares-settings: https://salsa.debian.org/Mobian-team/calamares-settings-mobian/-/merge_requests/22 * MR for mobian recipes: https://salsa.debian.org/Mobian-team/mobian-recipes/-/merge_requests/69 * Note: It is waiting for the new u-boot-menu with fdtoverlays and config fragment support. The new images would need the vccq support package and after testing it should be okay * Gnome-Software: Open a bug report requesting mobile support for software-properties-gtk (Used in Debian, not Mobian) * Latest version is from 2020.....and does not have mobile support. * See https://salsa.debian.org/pkgutopia-team/software-properties (upstream seems to be https://launchpad.net/ubuntu/+source/software-properties) * Would be nice for it to be ported for mobile support (GTK4?) * devrtz should poke Tobias about design input => ping devrtz on this topic; will open bug on BTS * our only patch on gnome-software removes the software properties because it's not adaptive * Q: Progress? => None * puremaps packaging: Has anyone reached out to the KDE packaging team? * https://salsa.debian.org/Mobian-team/puremaps-packaging * RFP is open https://bugs.debian.org/982986 * Status: s2geometry lib uploaded and accepted, still a lot of dependies to package * mobian-keyring to be reworked and re-uploaded to Debian * Q: Progress? => None yet * Universal images and tweakster? * integrated automatic firmware extraction for qcom-based devices: https://gitlab.com/mobian1/tweakster/-/merge_requests/1 * needs new rust deps in Debian, will update tweakster package once done * start with a generic sdm845 and/or qcom image + separate "FOSS phones" image? * Q: Progress? => None during the past 2 months * State of systemd user timers for gnome-clocks (https://pad.uni-hamburg.de/s/VlSduMhxt#) * maybe due to our custom PAM config? https://salsa.debian.org/Mobian-team/mobian-tweaks/-/blob/mobian/phosh/pam/phosh => this one will soon go away (i.e. once we switch existing installs to phog), maybe one problem less? * https://wiki.mobian-project.org/doku.php?id=birdie seems to do that? * Spaetz: Interesting, should ask them if it works. Afaik, systemd --user needs to be launched differently for this to work. * Installer issues: * calamares stable ABI * calamares-extensions uploaded and accepted * cleanup and review calamares-settings-mobian * Add support for pinephone vccq in the installer * Is it possible to install a package on the target partition after copy ? Yes -> install_bootloader * @Alex to look at * Q: Progress? * monitoring battery discharge; monitor CPU usage; monitor "real uptime" * Q: Progress? * Could be a part of GNOME Usage (with separate daemon) * lower sleep timeout to 1m => have it in our gsettings override at least, then figure out how to "coerce" upstream into adding such options (maybe based on device chassis type?) Q: Progress? => None * bookworm soft freeze: * have as much packages we want into Debian by this date * keep working on fixing bugs and stabilizing ou images until the release * promote bookworm images as the reference ones, advise people to reflash with that one and only apt upgrade over time * Debian packages we should maybe ask the current maintainers to update: * f2fs-tools * xkeyboard-config * pixman uploaded on 2022-11-11 so no action needed on that one * Package maintenance: we should clarify what should be maintained by the Mobian-team, and what should go to other packaging teams or under the generic "debian" group * Some will be in for a while (like gnome-contacts), others no * We should aim to get everything in Debian itself * Only maintain ones that we are upstream for, or have to carry patches for. => we should maybe have a clear policy regarding package maintenance in the Mobian-team group (same goes for DebianOnMobile-team) * a-wai to propose a draft and post on dev channel for reviews/comments/... * "Official" images: * should we keep building per-DE images (phosh only for now, but SXMO and plamo should be available soon) or ship a single image with all DE's present (using phog to select which session should be used)? * @a-wai would prefer shipping a single image * how should we handle the installer? keep the same process (same rootfs as ready-to-use images) or let users choose their DE(s)? (we could also have them input their desired username/full name as well) * distinguish weekly images and "blessed" images link to "blessed" image; how to bless image? needs time for testing. also device specific community driven curating? * ensure DE environments don't overwrite other DEs settings (e.g. PlaMo changing the system-wide GTK theme) * The tootle case