Differences between revisions 1 and 2
Revision 1 as of 2019-12-20 16:59:50
Size: 30
Comment: add to calendar
Revision 2 as of 2020-01-26 18:53:09
Size: 2242
Comment: add call notes
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

 * Shaarli dependencies packaging (James)
  * https://wiki.debian.org/FreedomBox/Contribute/Packaging/Shaarli
  * 2 of 4 dependencies uploaded or ready for upload
  * Plan to upload to buster-backports after shaarli reaches testing
  * php-pear team: https://salsa.debian.org/php-team/pear
 * Infrastructure upgrades (Joseph)
  * New process for creating !FreedomBox AMI
  * Updated AMI for demo server
 * Development instance ideas
  * Using packer to build vagrant box
  * Using systemd-nspawn instead of vagrant
   * better for performance
   * also consider docker or lxc
    * https://gitlab.com/docker-scripts/freedombox
    * docker should work well with gitlab CI
  * Using kvm backend for vagrant
   * better hardware support than virtualbox
   * Keep virtualbox option for development on windows/mac
 * Functional tests (Joseph)
  * Making functional tests faster
   * 25% speedup from merged improvements
    * Avoid multiple logins
    * Avoid extra navigation
   * Removing implicit waits - much more speedup
   * Running tests in parallel
    * Uses multiple browsers
    * Backup & restore is very flaky
     * Finding correct backup after it is created
    * pytest-xdist plugin
   * OpenVPN ECDSA key
  * Running functional tests in Salsa !GitLab CI
   * Gitlab CI runner
   * Run tests inside VM
   * Consider firefox headless mode
  * Running functional tests on stable+backports
 * Splitting functional tests (sunil)
  * Each module will have test_functional.py under tests/
   * .feature will contain BDD tests and
   * test_functional.py will contain step definitions, support utility methods and import of .feature file
  * Thoughts on BDD
   * Enforces good outline of tests, readable at top level
   * Not much advantage otherwise, makes it more difficult to control exact execution of tests
   * Proposal to remove feature file and step definitions, replace with pytest test case definitions
 * Splitting icons and actions
 * Calibre
  * Stable again
  * Python3 port is done
  * Perhaps we can look at calibre merge request again
  * It is meant for single user use-case. We can expose it a group of users who share the same library.

Progress call: 17:00 UTC

  • Shaarli dependencies packaging (James)
  • Infrastructure upgrades (Joseph)
    • New process for creating FreedomBox AMI

    • Updated AMI for demo server
  • Development instance ideas
    • Using packer to build vagrant box
    • Using systemd-nspawn instead of vagrant
    • Using kvm backend for vagrant
      • better hardware support than virtualbox
      • Keep virtualbox option for development on windows/mac
  • Functional tests (Joseph)
    • Making functional tests faster
      • 25% speedup from merged improvements
        • Avoid multiple logins
        • Avoid extra navigation
      • Removing implicit waits - much more speedup
      • Running tests in parallel
        • Uses multiple browsers
        • Backup & restore is very flaky

          • Finding correct backup after it is created
        • pytest-xdist plugin
      • OpenVPN ECDSA key
    • Running functional tests in Salsa GitLab CI

      • Gitlab CI runner
      • Run tests inside VM
      • Consider firefox headless mode
    • Running functional tests on stable+backports
  • Splitting functional tests (sunil)
    • Each module will have test_functional.py under tests/
      • .feature will contain BDD tests and
      • test_functional.py will contain step definitions, support utility methods and import of .feature file
    • Thoughts on BDD
      • Enforces good outline of tests, readable at top level
      • Not much advantage otherwise, makes it more difficult to control exact execution of tests
      • Proposal to remove feature file and step definitions, replace with pytest test case definitions
  • Splitting icons and actions
  • Calibre
    • Stable again
    • Python3 port is done
    • Perhaps we can look at calibre merge request again
    • It is meant for single user use-case. We can expose it a group of users who share the same library.