17 February 2022

# 17 February 2022 In Attendance ------------- - Present:DW, Alec, Ronald, Sonya, Marc, Clinton, Alex, Antti-Jussi, Davin - Regrets: Quick Updates ------------- ### What have you been working on lately? - **Clinton** - Current 3.3 plugin upgrade progress from Pitt - Done - akismet - betterPassword - clamAV - plumAnalytics - sushiLite - formHoneypot - TODO - siteSearch - inlineHtmlGalley - emailIssueTOC - editorialBio - **Ronald** - XML publishing workflows - plugin upgrades - template for OJS accessibility statements - Berlin Universities Publishing (Free University, Technical University, Humboldt University and Charitè) website and model journal setup (offical launch within the next month(s) - **Alex** - Nothing to report (vacations) - **Dulip** - [OJS DACH newsletter](https://github.com/ojsde/ojs-dev-dach/blob/master/berichte/2021-01.md) - Grant applications - **Alec** - OJS/OMP/OPS security releases due for host header injection issue (https://github.com/pkp/pkp-lib/issues/7649) - PKP developer hires nearly finished - PKP operations director hiring process continues - **AJ** - An EU application - **Marc** - Testing libreTranslator for forum and weblate. - OMP docker image (to be released next week) - "GA alternatives" workgroup. - **Davin** - "GA alternatives" workgroup. - (NGLP Analytics Dashboard Pilot project [Érudit]) - **Pierre** - "GA alternatives" workgroup. - Plugin upgrade Old Business ------------ * January meeting notes here: https://github.com/pkp/technical-committee/blob/main/meeting-minutes/2022-01-20.md * REMINDER - call for nominations for new Chair (for a two year term beginning at the April meeting). Deadline February 28! * LTS announcement and blog post has gone out: https://pkp.sfu.ca/2022/02/15/pkp-announces-long-term-support-lts-software-releases/ * Upgrade blog post ready to go: https://docs.google.com/document/d/1J9nsMH2d-b8Zo_Kk0Fv8KFKPzxAT9sRvPzBN7DwIcsA/edit# (thanks for your feedback!) * A comment needs review * Any updates from the group investigating analytics alternatives? (Marc, Davin, Pierre) * Larger discussion scoped down to something small and immediate * Two directions: * Publish a list alternatives without promising that they are GDPR compliant (e.g. Matomo or perhaps Plausible) * What is GDPR compliant (and who has authority to say)? Do we create a subcommittee to establish? * May have to develop knowledge around specific tools. * Will have local legislation to assess e.g. Quebec/Canada * Why do we need e.g. Google Analytics? Why not focus on COUNTER-style analytics? * Editors really want these (web stats). They have "good graphs". Prestige and demonstration of impact. * A checklist or wizard for journals? * starting with "do you really need google analytics?" * e.g. data must be hosted in EU, IPs must be anonymized, ... * Has Google reacted to GDPR challenge re: Analytics? * Bozana is already working on COUNTER/institutional subscription rewrite * NGLP is also a player on this. * Alec will send A-J details on this. * Sonya will share monthly call details. * Next steps * Ideas * Write a very short proposal to communicate as PKP (and send to documentation team to review). * Alternatively, going deeper and write down a "howto got statistics without GA" (explaining PKP tools, Plausible integration or Matomo). * finally, if is needed, build plugins for the alternatives. * Decision: subgroup will work with Nathalie on communications (e.g. blog post). "If you're worried about GDPR and analytics, here are some altneratives..." Standing Items -------------- * Testing working group update: February meeting cancelled. Next meeting March 3 New topics ------------ - PKP sprint in Helsinki: June 15-16 - April 1st decision to go/no-go (primarily Coronavirus) - Advertising to start next week for "hold the date" - PKP print in Colombia: June 29-July 1 - Spanish language - Marc's support proposals (added by Alec) - Polling/feature request additions to PKP support forum - Knowledge base tool - Documentation feedback request via Nate to file issue for admin guide in GitHub so it doesn't get lost: https://github.com/pkp/pkp-docs/issues > We have received documentation feedback about the following info needed for the stats guide - would anyone be able to shed light on it? > * what the salt file is used for > * where it should be put > * which permissions should be set > * if the file should be manually edited or not Next Meeting ------------ **March 17, 8 am Pacific time** (note to European members - we have a time change so this meeting will be an hour earlier than usual!)