---
# System prepended metadata

title: November 4 2021

---

# November 4 2021
8:00am Pacific time

In Attendance
-------------

- Chair: Antti-Jussi
- Present: Alec, Andrew, Rondinelli, Ronald, Sonya, Dulip
- Regrets:

Introduction
------------
- Introduction of new members
    - Andrew from Penn State
        - University Library runs OJS install with ~12 public journals
        - Recently also involved in systems work (containerization; kukbernetes; etc)
    - Antti-Jussi contacted Danish installation admins; they will communicate back if there are good candidates to join

- Review terms of reference
    - Ready to publish/share - Sonya can share with James / directors and copy Alec. Already shared with Dev team.

Brainstorming (in rough priority order)
-------------
* upgrade testing
    * Community testing plan for major releases(Alec)
    * Representative (real world) upgrade testing (Alec)
    * determine what needs to be tested consistently with each upgrade (Sonya)
    * Find ways to use big installation and real life data for upgrade testing (AJ)
    * consider platform dependecies (Ronald)
    * In progress and a prototype for PKP: https://github.com/pkp/pkp-lib/issues/7301
    * Proposed scopable tasks:
        * Try an upgrade on a release candidate of 3.4
            * Establish a set of tests for each of us to run
            * Use real world data
                * Run upgrade tests
                * Document what each dataset typifies
                    * What features are covered? (e.g. Categories; multijournal; large dataset)
                    * What starting version is the upgrade covering?
            * Method to package up what's "necessary"
                * How to create a test copy (tooling or documentation)
                * How to sanitize/sandbox real world data
            * Template for reporting results
* performance testing
    * Front-end performance testing (Dulip)
        * Large issues
        * Large search indexes
    * Determining a plan for reducing the number of DB queries per request (Alec)
    * Caching proxy (Alec)
    * Reviewer search bottleneck; user adminstration bottleneck (Alec)
    * Building test script or automated tests for performance testing
    * statistics export performace (Ronald)
    * Filed and a priority for 3.4.0: https://github.com/pkp/pkp-lib/issues/7304
    * Possible tasks:
        * Gather issues into Github project
        * Test indexing speed for 3.4
        * Test search speed for 3.4
        * Testing for https://github.com/pkp/pkp-lib/issues/7304
* writing tests (or coordinating writing tests with community)
    * Cleaning up / fixing unit testing; introducing "reference" example (Alec)
    * Creating similar tests for all three applications "a standard" (AJ)
    * Identifying and writing tests for far-flung areas of software (e.g. Categories)
* conducting pre-release testing in real production environments
    * Choosing smaller and bigger installations and work together with them and come up with a plan for consistent testing of new versions. Including upgrade testing (AJ)
* creating and sharing documentation on how to test or how to write tests
    * "Reference" test set for each type of test -- plugin tests, integration tests, unit tests (Alec)
* coordinating testing activities with community members
    * recruit community testing partners and provide them with a testing plan (Sonya)
    * Developer Community  engagement in (German Speaking countries) (Dulip)
* studying and recommending tools for testing
    * Replacements for Travis (Github Actions etc) (Alec)
    * Docker (circle-ci?) (Andrew)
* developing data validation tests
    * Building out "pre-flight" upgrade testing (Alec)
    * export plugin testing / validate exported data (Ronald)
    * Testing  specific plugins (Dulip)
    * consider methods for pre-upgrade testing of config/data integrity? (Andrew)
* communicating with or surveying the community about timelines and schedules for testing
* maintaining and updating admin documentation
    * “How to Upgrade” guide
    * Automated screenshot generation (Alec)

Prioritization of projects
---------

- Brief discussion on contents of each item 
    - do we agree what the content is?
    - do we have some items that could/should be combined?
    - are we missing something?
- Priorization of projects
    - which one's are most important?
    ![](https://i.imgur.com/yzCyxgG.png)

    - should the chosen projects have different nature: purely technical / more concerning documentation
    - choose one or two projects? Maybe even 3 if one is less technical?
- Next steps for the chosen projects
    - Upgrade testing
        - Members: Antti-Jussi, Sonja, Alec, Ronald, Andrew
    - Performance testing
        - Members: Alec, Antti-Jussi, Rondinelli
- How to proceed with the remaining items

Other topics
------------
- New member candidates

Next steps
----------
- Sonya will take the Terms of Reference to James (CC Alec)
- Alec will get a Slack channel created

Next Meeting
------------

- Time/Date: December 2, 8:00am Pacific time
- Chair: (wing it / Alec)
- Projects: Optimization and upgrade testing
