= Progress call: 17:00 UTC =

 * Android app
   * Wasn't covered in the topics submitted for the Summit
   * How does it fit into the big picture?
     * First boot experience:
       * self-signed certificate
       * freedombox.local not always resolving
     * Most use cases possible with Plinth on mobile
     * Planned as installation guide
     * Goals, differences with plinth
     * Break down issues into more granular tasks
 * Lime 2 rev. H and above not working
   * New Ethernet controller - not supported by mainline kernel yet
   * Suggest to report Debian bug or ask on debian-arm
   * Possibility to work-around in freedom-maker (temporary solution)
   * Current shipping is rev. K
 * Lime 2 Buster image ready
   * In https://ftp.freedombox.org/pub/freedombox/nightly/
   * Probably link to on Buy page for buying the box
   * Stable updates are slower than testing - most packages don't change, only security updates.
   * Testing is also an option, requires some technical skill.
   * Stable + backports is another option.
   * Add option to plinth to upgrade to testing.
 * plinth Marked for autoremoval on 11 December due to python-testfixtures: #912184
   * Working on patch, will post to bug report.
 * Backup module (fonfon), remote backups:
   * should managing 'remote locations' be generalized, are they needed by other modules than backup?
     * basic example layout of creating remote borg repository:
       * https://screenshots.firefox.com/FeSARXP9XONtKRIy/freedombox
     * possible other modules: Deluge, Transmission - to store downloaded files remotely
     * Suggestion to add to Storage module
   * backups action script will set environment password variables when executing borg
   * public/private key authentication has to be set up manually for a start
   * is it OK to store ssh passwords in plinth KVStore - better ideas?
     * Option to use SSH key pair.
   * can we re-use an admin password for the borg repository encryption?
     * we'd have to make sure that the repo key password is updated when admin user is deleted or changes password
     * So, for the beginning we'll stick to separate passwords
 * consider other logging filesystems? https://en.wikipedia.org/wiki/NILFS
   * Snapshot on every write.
 * Working on a daemon and configuration syntax to expose services
 * remove apps procedure? (mray)
   * create issue