openteachermaintainers team mailing list archive

[Milan Boers <mail@xxxxxxxxxxxxx>]

Blueprint changed by Milan Boers:

Whiteboard changed:
  GPG handling:
  Command: gpg(.exe) --status-fd 1 --homedir gpghome --verify updates.json.asc updates.json
  If verifying succeeded, the exit code is 0.
  If public key was not found, the exit code is 2.
  
+ Verifying also succeeds when the key is imported, but not trusted. Since
+ this is local, and we use our own gpghome, I don't believe this matters.
+ We can treat all imported keys as trusted, and all unknown keys as
+ untrusted. This is what the current revision does.
  
  This will change the way OpenTeacher is distributed.
  ~milanboers proposes we do this:
  - When we have enough stable new modules (modules that were not in any previous releases), or there are changes to the module manager, we release a new OpenTeacher version.
  - Bugfixes and important updates of modules are pushed through the update manager.
  
  ~marten-de-vries says:
  - All updates are pushed through the update manager, we only release versions now and then to make the updates after the download not too big.
  
  ~Guus asks:
  - Will translations also be updated trough the manager?
  ~marten-de-vries: Yes!
  
  Discussion points:
  - Do we alert the user when an update is available, do they have to look for theirselves, or do we secretly automatically push them? Linux users are not used to updates within applications.
  
  By default the user gets asked, there's an option to automatically (not)
  install updates the next time.

-- 
Updates for modules from OpenTeacher
https://blueprints.launchpad.net/openteacher/+spec/update-manager