Or milestones of the roadmap :
Those are all worthwhile targets. I’d put “Keep up with the changing world around you” on the very top though. Activities like that are low profile but important (and would resolve a large amount of complains raised in the forums and elsewhere). I’d use these priorities:
- keep up with kernel releases (which means going from 6.6. to 6.10) and then keep up (to be able to leverage advancements there)
- keep up with Debian releases (which means going from Bullseye to Bookworm and have a working / installable suite tracking Trixie to not fall behind as this matures to have a variant available once Trixie releases thus lowering the backporting burden and benefiting from what Debian already ships
- keep up with Upstream software releases (GNOME, Phosh, Pipewire, libcamera, …)) backporting important components affecting mobile again benefiting from what improved and improves there.
All of these fit a subscription model nicely as it’s continuous maintenance work. It would also make the PureOS distribution become a more attractive target for Linux Mobile development thus opening the possibilities to attract more contributors.
Next up would be
- Mainline remaining kernel bits so 1. becomes simpler
Once you can go with the flow tackling the roadmap will become so much easier as you have an up to date environment and can leverage what is there easily. Having worked on all of the above in the past I’d say that this requires a fair amount of continuous subscriptions but it would do wonders for users and developers.
EDIT: I certainly hope i vastly underestimate the amount of subscriptions and there will be enough to tackle everything at once 