4 quick questions

4 quick questions:

  • Do we let the user do a manual system update on battery power?
  • Do we do the automatic security updates on battery power?
  • Do we allow long transactions (e.g. update kernel) to be scheduled when we are low on battery power?
  • Do we make these options configurable in just gconf or in the UI?

Something like that?

Published by


Richard has over 10 years of experience developing open source software. He is the maintainer of GNOME Software, PackageKit, GNOME Packagekit, GNOME Power Manager, GNOME Color Manager, colord, and UPower and also contributes to many other projects and opensource standards. Richard has three main areas of interest on the free desktop, color management, package management, and power management. Richard graduated a few years ago from the University of Surrey with a Masters in Electronics Engineering. He now works for Red Hat in the desktop group, and also manages a company selling open source calibration equipment. Richard's outside interests include taking photos and eating good food.

One thought on “4 quick questions”

  1. 1. Yes, but see 3. 2. Yes, but see 3. 3. You have a way of approximating the length of pending operations, right? So why not just prompt the user if they've scheduled jobs which will take longer than is estimated left in the battery? Actually, simply disabling this entirely (with a gconf key to enable it) is probably safer, given the likely effects of running out of battery widway through a dist-upgrade (i.e. complete system death). 4. No. You don't make these options configurable (with the caveat for the safe bet on 3). UI should be strictly verboten. – Chris

Comments are closed.