Thursday 15 May

# Thursday 15 January 2026 In Attendance ------------- - Present: - Emma, Sebastian, Carolina, AJ, Davin, Alec, Marc, Dulip - Regrets: Martin Brändle Meeting at: [Former notes archive](https://github.com/pkp/technical-committee/tree/main/meeting-minutes). Quick Updates ------------- ### What have you been working on lately? - **Marc** - XMas vacations (extended) - New OJS 3.5.0-3 docker image. - OJS workflow documentation. - **Sebastian** - Final touches to Individualize Theme, Google Fonts Plugin, Partner Block Plugin and [Open Science Badges](https://www.cos.io/initiatives/badges) [Plugin](https://github.com/NateWr/openScienceBadges) - Localisation for German - Last bug fixes - Then application for plugin gallery (3.3, 3.5) - **Davin** - JATS upgrade for OAI-PMH, JATS 1.1 --> 1.2 (versions of [schematron used in tests](https://github.com/pkp/oaiJats/blob/main/.github/actions/tests.sh) to be discussed) - **AJ** - CRAFT-OA reporting and final work - Data Citations work for 3.6 - Fixing small issues after 3.4 upgrade - **Carolina** - Improvements to the Dataverse plugin (with Lepidus). It'll be possible to automatically pick up the same fields that are marked required in Dataverse - Started work on updating plugins for 3.5 Agenda ------ 1. Housekeeping - Discussed the meeting time, sticking with the current one 2. PKP Survey project - Recurring user survey, every 2 years: how do you feel about this, suggestions etc. - Discussions on what the survey should be and other details - Marc: raised the earlier survey and how the feature requests forum was designed to easily extract categories for a periodic survey. - Alec: move to forum with feature requests has been problematic because people do not feel heard. Some still go to Github with feature requests. - Marc: We need a PKP participation methodology - a workflow - Alec: the tech committee could be involved in some preparation work. Identify other projects/software with same challenges and what they are doing. 4. Question: Beacon data gaps - Make sure that the surveys is capturing things that the beacon data is not covering - Alec: The beacon could be turned off. Missing data has been checked with human checks, find out whether someone sees missing journals. - Marc: we need respect the privacy of the journal data, but at same time would be great to get detailed feedback (enabled plugins, versions, users...) from the ones that like to share as they can be a good source of data to detect what the community does. 5. Check on WIPs 6. Topics list refinement - OMP terminology - AJ: this has been discussed in Zoe's meetings. Especially a discussion about "Press" in OMP - should be more neutral and wider term - Marc: This is not the most important topic because it is discussed also elsewhere. Other words discussed is the OMP name: for example "Books" instead of "Monographs". Zoe is working on this. - Emily: no need to discuss right now, later if needed - OxS decoupling and 12 factors - Marc: fits very well to the discussions we should have in the technical committee. But how to chop this big proposal to smaller parts that we could do. - Alec: PKP has a feature based roadmap, but hard to see what is changing in the structure of the software. We could use such a secondary roadmap. This would make it more clear the direction of the software and answer suggestions like this more clearly. This Committee could tackle some concrete work without creating dedicated working groups, perhaps by extanding the meeting time, thus avoiding work between our meetings (the PKP Docs group works like that). 7. Discussion topic: Core vs. Plugin - Alec: A forthcoming event for plugin developers, more details coming soon from Urooj. - Marc: More a discussion whether we want to develop big-core or small-core, as other CMS discussed years ago. Small core will probably easier to maintain for PKP, but harder work will need to be done in plugins. - Alec: we are already going towards a big-core solution. - Marc: But the recommendation for third party developers is still "implement a plugin, don't try to change the core"? - Alec: Depends of the context. Some things can be easily extended with a plugin and some things not so easily. We can also widen the code base by taking more contributions to the core. New topics list: https://hackmd.io/@ehopkins/rkZiri-Qbl/edit Pending work ------------ Next steps about [KM tool](https://github.com/pkp/technical-committee/blob/main/meeting-minutes/2024-07-18.md): - [ ] Group to try various proofs of concept: - [ ] AI / chatbot options (Martin) - [x] FAQ specialized tools (Marc) - [ ] FAQ area in forum for guiding support / Github Discussions for policies (Alec) Next steps about [Releases](https://hackmd.io/YOfEL0KdRwiV7wz2_TXA-w?view) - [ ] Alec's releases the gantt diagram developemnt - [ ] Talk with Coms to create the page at xxx. ------- Quick Updates ------------- ### What have you been working on lately? - **Dulip** - CRAFT-OA - GDPR reviwer invitation - XML Leanring Course for EDCH (European Diamond Capacity Hub) - Texture Plugin (support importing external API endpoints) - LensGalley Plugin (node update, partially responsive design) - **Emily** - work on fixing IR metadata for Library and Archives Canada harvesting and setting up some digital preservation stuff too - work towards layout stuff for new Library Freedom Project journal - CARL event on new repository article (https://www.carl-abrc.ca/event/canadian-repositories-community-of-practice-december-call-current-challenges-and-future-directions-for-institutional-repositories-snapshots-from-the-literature/) - **AJ** - CRAFT-OA reporting and final work - Data Citations work for 3.6 - Fixing small issues after 3.4 upgrade - **Martin** - Updated two platforms to OJS 3.4.0-10 - Testing OJS 3.5.0-2, adapting plugins - different tasks regarding repository + AI - **Marc** - OJS 3.5 testing (behind a reverse-proxy). - Update Docker images. - [ARTS plugin](https://github.com/MejorAbierta/ARTSPlugin) closing. - Extracts information from OJS in JSON, HTML or CSV formats -- e.g. KPIs from jounrals, what version of OJS, gender information, etc. Can use arbitrary SQL. - Recovering from the flu. - **Sebastian** - Finalizing the second development iteration with Nate on the [Individualize-Theme](https://github.com/NateWr/individualizeTheme) and the additional plugins generated within the project ([DSGVO-conform Google Fonts](https://github.com/NateWr/googleFonts), [Inline HTML Galleys](https://github.com/NateWr/exampleIndividualizeChild), [Open Science Badges](https://github.com/NateWr/openScienceBadges) and [Partner Logos](https://github.com/NateWr/partnerLogos)) - Accessibility Adaptations - Bugfixes and Changes for 3.5 - --> Aim provide to the plugins via gallery once we finalized the project and issues [12129](https://github.com/pkp/pkp-lib/issues/12129), [12133](https://github.com/pkp/pkp-lib/issues/12133), [12141](https://github.com/pkp/pkp-lib/issues/12141), [12067](https://github.com/pkp/pkp-lib/issues/12067) and [12134](https://github.com/pkp/pkp-lib/issues/12134) are solved - Added [User-Documentation](https://www.slub-dresden.de/fileadmin/groups/slubsite/Ver%C3%B6ffentlichen/PUBLIA_-_SLUB_Open_Publishing/Doku_Individualize_Theme_Herausgebende.pdf) <- Translation will be provided soon - **Alec** - Working towards big OSS ORE deliverable in February - Kevin's replacement (Operations Director) is semi-announced! - **Ronald** - Plugin upgrades - SeDOA XML workflow business Agenda ------ - Notetaking rotation volunteers - It helps to have at least 1 person designated in rotation who is mainly in charge of notes - Please follow up in Mattermost! - Quick update on feature requests working group proposal - Emily joined an internal PKP meeting about prioritization in general -- this is a bigger discussion than expected - Topics list -- can we eliminate or consolidate any topics, or define more clearly what our goals are for the discussions? - check in on pending work - Discussion on most-voted topic: How to show OxS requirements?: php version, php plugins, HW requirements… Notes ----- Plugins vs. built-in features - Main vs. plugin? - Open Repositories integrations (SignPosting, FAIRiCat, COARNotify). Pending work ------------ Next steps about [KM tool](https://github.com/pkp/technical-committee/blob/main/meeting-minutes/2024-07-18.md): - [ ] Group to try various proofs of concept: - [ ] AI / chatbot options (Martin) - [x] FAQ specialized tools (Marc) - [ ] FAQ area in forum for guiding support / Github Discussions for policies (Alec) Next steps about [Releases](https://hackmd.io/YOfEL0KdRwiV7wz2_TXA-w?view) - [ ] Alec's releases the gantt diagram development - [ ] Talk with Coms to create the page at Old Business ------------ Other topics ------------ :one: (In progress) How to show OxS requirements?: php version, php plugins, HW requirements… :two: Core vs. Plugin-Approaches for new features. - Feature by feature: when to have a plugin, when to make core (e.g. RoR, ORCiD, probably funding is next) - Community maintenance standards/obligations - "Plugin hell" -- experienced by other platforms like Filemaker, Wordpress, etc. - Plans for XML process - If we aren't sure which tool will be most successful, use plugins to allow multiple options - Reasons for plugins? - Back-end requirements (something that involves exotic server requirements) - Uncertainty over best tool among many (e.g. DataCite, CrossRef) :three: Open Repositories integrations (SignPosting, FAIRiCat, COARNotify). :four: Ideas for the Health Check plugin. - Journal Metadata vs. Technical Health Check (booth associated with that topic term) :five: Research integrity checks (e.g., looking for papermills, suspicious activies (author and reviewer being the same person), fast journal turnaround (peer review happening too quickly)** :six: [plugin API endpoints](https://mattermost.publicknowledgeproject.org/pkp/pl/4idzz8ths7dc8er8b1qc719dsc) (by Nate). - Already a solution proposed: https://github.com/pkp/pkp-lib/discussions/11991#discussioncomment-15196485 :seven: personal data preservation & GDPR (by AJ). - "Right to be forgotten"-Implementation as well as Transparancy Rights - Which places in OJS store personal data that would have to be considered? --> Guidance for Administrators needed - Currently requirements from ORE --> TIB + PKP work on :eight: [SBOM](https://forum.pkp.sfu.ca/t/software-bill-of-materials-sbom/95822/13?u=marc) (by Jon) :nine: FAQs management (by Marc) - Document available for review by the committee :keycap_ten: [OxS decoupling and 12 factors](https://forum.pkp.sfu.ca/t/decoupling-the-application-for-cloud-native-development-and-deployment-scenarios-according-to-the-twelve-factors-12factor-net/97143/3) (by Jon) :page_with_curl: ToR update :electric_plug: metadata and plugins (started by Juan I think) -- FWIW when this was discussed it sounded like Mike wanted to follow up on something about funder metadata before we discussed further but I can check in with him :books: OMP terminology (and redefinition). Next Meeting ------------ Third Thursday of the month: **NEW** 7am Vancouver time A note on note taking ----------- Note taking is shared -- anyone may edit the document. Alec will upload to the minutes page 24 hours after the meeting to allow for any final edits or updates committee members have. ******************************* -------- # Thursday 20 November In Attendance ------------- - Present: Emily, Sebastian, Marc, Alec, Ronald, Martin - Regrets: Meeting at: [Former notes archive](https://github.com/pkp/technical-committee/tree/main/meeting-minutes). Quick Updates ------------- ### What have you been working on lately? - **Emily** - Open Access Week Carnival/workshops ([Price of Knowledge quiz](https://usask.libwizard.com/f/price-of-knowledge)) - Meetings with MC about Feature requests - Investigating XML publishing workflows for [Library Freedom Journal](https://ojs.library.queensu.ca/index.php/lfj/index) (thanks those who weighed in on Mattermost!) - finished teaching most recent round for ALA Repositories course - **Martin** - mostly engaged with UZH publication repository migration issues (e.g. processing 180 million accesses for statistics, presentations of project at various meetings), not much time for OJS - Theme changes for multilingual display of a journal (OJS 3.4.0-9) - Porting a status filter for submissions developed by my colleague Kristian to a OJS 3.4 journal - testing publication facts label plugin - it crashes with imported publications - onboarding meetings for K8s OJS / OMP container hosting - **Marc** - Working with [MejorAbierta](https://github.com/MejorAbierta/) fellows (ARTS plugin it's promising). - Finishing Toolkit with CRAFT-OA. - Dealing with Drupal upgrade (always even harder than OJS). - **Ronald** - OJS 3.5 plugin upgrades - SeDOA XML-workflow business (e.g. establishing am XML discussion group) - New SeDOA (German Diamond OA Capacity Hub) coworker to develop on XML worflows and in particular to improve Pandoc (first commit already done) - **Sebastian** - Working with Nate on the [IndividualizeTheme](https://github.com/NateWr/individualizeTheme) until End of Year - Experimenting with Author Contract Generation in OJS - Alec: OJS/OMP/OPS 3.5.0+ contain MPDF already for PDF export of peer reviews -- see `lib/pkp/api/v1/reviews/PKPReviewController.php` in the `generatePDF` function - **Alec** - Releasing OJS, OMP, OPS builds for 3.3, 3.4, 3.5 today/tomorrow - There are some XSS / security fixes (nothing super critical but worth releasing/upgrading) - 3.5 release will be 3.5.0-2; expecting LTS stamp to go on 3.5.0-3. - Lots of internal silo-breaking conversations! - Plugin maintenance - Release management - Prioritization - Email delivery Agenda ------ - review updates - Alec: typesetting/body text options - Emily: Feature Requests Working Group planning and discussion - questions from previous meeting with MC: https://docs.google.com/document/d/1yLzIforPeBLn-FgjnRo8xraczeYkmltzSPB1JfZH2_c/edit?usp=sharing - notes Emma took: https://docs.google.com/document/d/13o2TYyUf5iXlPQISzTM5rfXna6ENrWpVLJl43FOoQDM/edit?tab=t.0#heading=h.6mezyfdbeqie - I will be at senior staff meeting later in the day to discuss who should be involved and how we will operate so it would be great to summarize some key points from TC perspective - Updates and additions to the discussion topics list -- can we eliminate or consolidate any topics, or define more clearly what our goals are for the discussions? Notes ----- ### Typesetting body text options Review of body text editing plans and various conversions; more to come via the Production Workflows working group (PKP + various community stakeholders) followed by workshops and webinars (external) Pending work ------------ Next steps about [KM tool](https://github.com/pkp/technical-committee/blob/main/meeting-minutes/2024-07-18.md): - [ ] Group to try various proofs of concept: - [ ] AI / chatbot options (Martin) - [x] FAQ specialized tools (Marc) - [ ] FAQ area in forum for guiding support / Github Discussions for policies (Alec) Next steps about [Releases](https://hackmd.io/YOfEL0KdRwiV7wz2_TXA-w?view) - [ ] Alec's releases the gantt diagram developemnt - [ ] Talk with Coms to create the page at Old Business ------------ Other topics ------------ I think Alec's topic and some feature requests discussion would be helpful so those will make the agenda -- it would be great if we could summarize the FR situation a bit from our perspective -- but here are all the topics proposed! maybe tomorrow we can have a brief chat about if all of these should be on our list or if some will be taken care of elsewhere but here they are for now: :one: (In progress) How to show OxS requirements?: php version, php plugins, HW requirements… :two: Core vs. Plugin-Approaches for new features. * Feature by feature: when to have a plugin, when to make core (e.g. RoR, ORCiD, probably funding is next) * Community maintenance standards/obligations * "Plugin hell" -- experienced by other platforms like Filemaker, Wordpress, etc. * Plans for XML process * If we aren't sure which tool will be most successful, use plugins to allow multiple options * Reasons for plugins? * Back-end requirements (something that involves exotic server requirements) * Uncertainty over best tool among many (e.g. DataCite, CrossRef) :three: Open Repositories integrations (SignPosting, FAIRiCat, COARNotify). - Opportunities for implementing :four: Ideas for Health Check. - What would outstanding concerns for this be? - See: Metadata preflight checks for publishing https://github.com/pkp/pkp-lib/discussions/12008 - Additional opportunities: technical checks on installation health - We always talk about both when we talk about Health Check! :five: Research integrity checks (e.g., looking for papermills, suspicious activies (author and reviewer being the same person), fast journal turnaround (peer review happening too quickly) * Big-picture conversation or what happens in OJS? * PKP discussing what/whether we want to have a role in communicating with the community about AI papermills; more to come :six: [plugin API endpoints](https://mattermost.publicknowledgeproject.org/pkp/pl/4idzz8ths7dc8er8b1qc719dsc) (by Nate). * Has led to a discussion, proposal and PRs. https://github.com/pkp/pkp-lib/discussions/11991#discussioncomment-15196485 :seven: personal data preservation & GDPR (by AJ). * GDPR support around user interactions is overall OK but... * Right to be forgotten vs academic record-keeping requirements * Limited options in OJS e.g. merge option (not a good option) -- may leave data e.g. in the logs * Both technical and policy discussions :eight: [SBOM](https://forum.pkp.sfu.ca/t/software-bill-of-materials-sbom/95822/13?u=marc) (by Jon) * Marc's summary: "Jon suggested that OJS should provide a formal Software Bill of Materials (SBOM) in a standard format such as SPDX or CycloneDX to clearly list all software components and dependencies in a machine-readable way." * This would support security analysis, automation, and CI/CD integration, complementing existing package manager files rather than replacing them. * All agreed it's a good idea; need to find practical next steps. :nine: FAQs management (by Marc) * Need to pick up review of FAQ management tools proposed/captured by Marc (it's in HackMD and Mattermost) :keycap_ten: [OxS decoupling and 12 factors](https://forum.pkp.sfu.ca/t/decoupling-the-application-for-cloud-native-development-and-deployment-scenarios-according-to-the-twelve-factors-12factor-net/97143/3) (by Jon) :page_with_curl: ToR update :electric_plug: metadata and plugins (started by Juan I think) -- FWIW when this was discussed it sounded like Mike wanted to follow up on something about funder metadata before we discussed further but I can check in with him :books: OMP terminology (and redefinition). Notifications: @asmecher |@ajnyga | @dulip.withanage | @giotta | @ronste | @rick_hoover | @jtakeda | @alex.mendonca | @mpbraendle | @sschmidt | @emily_hopkins | @marc |@carolina.tanigushi Thanks! Emily Next Meeting ------------ Third Thursday of the month: **NEW** 7am Vancouver time A note on note taking ----------- Note taking is shared -- anyone may edit the document. Alec will upload to the minutes page 24 hours after the meeting to allow for any final edits or updates committee members have. ******************************* -------- # Thursday 16 October In Attendance ------------- - Present: Marc, Alex, Carolina, Emily, Davin, Martin, Alec, Dulip - Regrets: Meeting at: [Former notes archive](https://github.com/pkp/technical-committee/tree/main/meeting-minutes). Quick Updates ------------- ### What have you been working on lately? - **Alex** - Adapting PREreview and DocMap plugins for OPS 3.4 (with Lepidus) - Preparing Carolina Tanigushi to take over (*cries*) - **Dulip** - integration of External TIB ORKG Service to create publications for Jouranl publishing ( [API](https://orkg.org/simcomp/thing/export?thing_key=R643100&thing_type=REVIEW&format=XML) , [original Review](https://orkg.org/reviews/R643100) - CRAFT-OA Conference (XML Plugin presentation for TEI <-> JATS and service validation) - TIB Internal XML pipeline for JATS validation and reference parsing - 3.5 Upgrade plugins - Tweaking a terraform, docker local installation bash script to replace bash based local development environment - CRAFT-OA GDPR - Reviewer workflow - **Sebastian** - **Marc** - CRAFT-OA Conference (missing a plane) - Collaboration with TIB (Jon) to improve the official docker images. - CRAFT-OA Toolkit writing. - Collaboration to finish the development a new Advanced Report Tool plugin (ARTs). A yaml define the data to get from DAO, SQL or PHP scripts. Results are exposed as JSON in API endpoints or extracted in CSV, HTML or ZIP formats. - Collaboration to improve the openID plugin: Multiple authority sources. - Meet the experts workshop about OJS containers. - **Davin** - **AJ** - **Ronald** - **Martin** - mostly engaged with ZORA repository work - meeting on OJS on K8s - **Emily** - Open Access Week preparation (workshops and carnival) - Finishing our OJS hosting service project documentation at USask so it can be a regular service - **Alec** - Preprint workflow in OJS is now demonstrable - M16 OSS ORE deliverable (today!) - Public commenting, Zenodo, DOAJ, searching & Frascati, tasks & discussions, ... - Working with SciFlow/OS-APS on body text editor - Structured citations got merged -- thanks TIB!!! - Security and updates discussion -- [memo published](https://pkp.sfu.ca/2025/10/15/keep-your-ojs-installation-secure-with-updates/), I'll put together a video covering within-branch upgrades - Alec to come up with a strategy on better integration of CVEs into PKP's internal process -- reduce noise with multiple places to look. - Plugin community, updates, and sustainability coming up internally -- likely to arise here too. - Added Sentry support -- https://github.com/pkp/pkp-lib/issues/11875 Agenda ------ - review quick updates -- Craft OA! - Welcome Carolina - Update on meeting with Members Committee re: Feature Requests working group - Topic #1: OsX requirements - Topic #4: Health Check plug in Notes ----- - Topic #1: OsX requirements - Alec: Better show ojs versions. A proof of concept was done with the gantt diagram but we have an issue with the license. Going ahead as we are acting in good faith. - Text explanation is ready and will be published soon. - Requirements included in [composer](https://github.com/pkp/pkp-lib/blob/main/composer.json) and in the [repo README](https://github.com/pkp/ojs) - LTS page draft doc: https://hackmd.io/YOfEL0KdRwiV7wz2_TXA-w - Topic #4: Health Check plug in - CP / PKP team is working on a plugin for Coalition Publica; this will likely serve as a good template for others. - Additional brainstorm ideas: - **Server Environment** - PHP version and required extensions compatibility. - Correct permissions in `public/`, `cache/`, `files_dir/`. - Disk space, `memory_limit`, and `max_execution_time`. - Valid HTTPS configuration and SSL certificate. - URL redirections (ensure main endpoints exists) - **Database Integrity** - Check for missing or broken keys and indexes. - Detect duplicate records and orphaned references. - Ensure schema consistency with the installed OJS version. - Periodic table optimization. - **File Integrity** - Match between database records and `files_dir` content. - Verify permissions and ensure no public HTTP access. - Validate hashes or checksums of critical files (`config.inc.php`). - **System Configuration** - Validate `config.inc.php` "version". Check values and external executable paths. - Verify scheduled tasks (*cron jobs*). - Check integrity of `registry/` and `locale/` directories. - **Plugin Compatibility** - Confirm plugin compatibility with the current OJS version (or run the pugin in a try-catch) - Identify obsolete or conflicting plugins. - Verify plugin origin or digital signature. - **Installation Health and Performance** - Measure frontend and backend response times. - Check cache status and error logs. - Verify PKP PN indexing and outgoing mail queue size. - **Pre-upgrade Checks** - Ensure recent database and file backups. - Confirm consistent DB schema versions across all journals. - Run upgrade *dry test* and validate migration scripts. - **Editorial Data Integrity** - Detect inconsistent submission or article states. - Check for incomplete or invalid metadata (DOI, ORCID). - Identify stalled or overdue editorial tasks. - Alec: Many of these are technical in nature; purpose of health check could also be editorial. - Many of the tech elements represent common pitfalls -- maybe invest time in building a bridge over the pit, rather than dropping a ladder in :) - Sidebar: dev leads are talking internally about a technical roadmap. Current roadmaps are feature driven, and technical roadmap is not well articulated anywhere. More to come. Sentry -- Sentry support was added here for release in 3.6; it'll be easy to back-port: https://github.com/pkp/pkp-lib/issues/11875 https://develop.sentry.dev/self-hosted/ https://github.com/getsentry/sentry?tab=License-1-ov-file#readme Pending work ------------ Next steps about [KM tool](https://github.com/pkp/technical-committee/blob/main/meeting-minutes/2024-07-18.md): - [ ] Group to try various proofs of concept: - [ ] AI / chatbot options (Martin) - [ ] FAQ specialized tools (Marc) - [ ] FAQ area in forum for guiding support / Github Discussions for policies (Alec) Old Business ------------ Other topics ------------ - :one: (In progress) How to show OxS requirements?: php version, php plugins, HW requirements... - :two: Core vs. Plugin-Approaches for new features. - :three: Open Repositories integrations (SignPosting, FAIRiCat, COARNotify). - :four: Ideas for the Health Check plugin. - :five: Research integrity checks (e.g., looking for papermills, suspicious activies (author and reviewer being the same person), fast journal turnaround (peer review happening too quickly) - :six: long-term handling of personal data (GDPR, right to be forgotten, user accounts, anonymization of reviewer data vs. data requirements for open peer review) Next Meeting ------------ Third Thursday of the month: **NEW** 7am Vancouver time A note on note taking ----------- Note taking is shared -- anyone may edit the document. Alec will upload to the minutes page 24 hours after the meeting to allow for any final edits or updates committee members have. ******************************* -------- # Thursday 18 September In Attendance ------------- - Present: Alex, Alec, Ronald - Regrets: Meeting at: [Former notes archive](https://github.com/pkp/technical-committee/tree/main/meeting-minutes). Quick Updates ------------- ### What have you been working on lately? - **Alex** - SciELO Preprints upgraded to OPS v3.4! -- dealing with post-upgrade issues that surfaced. - **Dulip** - **Sebastian** - **Marc** - **Davin** - **AJ** - Had our second OJS & OMP editor's day https://tsv.fi/fi/uutiset/teemapaiva-open-journal-systems-ja-open-monograph-press-jarjestelmia-kayttaville-0 - Migrating Edition.fi to OMP 3.4 in the end of September (last test upgrades done this week), Journal.fi follows in the end of October. Moving to 3.5 in spring if everything works fine. - Finishing work in CRAFT-OA project which ends in December - **Ronald** - Working on fetching OJS statistical data from different OJS installations - plugin upgrades for 3.5 - **Martin** - Mostly engaged with migration/go-live of ZORA repository to DSpace-CRIS, so not much time for OJS. - Together with Alec: indexNow plugin (alternative to sitemaps, see https://www.indexnow.org and https://forum.pkp.sfu.ca/t/indexnow-indexing-of-journals-with-bing-yandex/96967 ). PR for sitemap generation tool. - **Emily** - Our new OJS hosting service at USask is live and has three journals in it! - I moved! :) - **Alec** - Performance work on ojs-stable-3_5_0 -- working towards 3.5.0-2, which might be a good LTS candidate - Working on openSearch, Frascati vocabulary and faceting -- see Q3 dev leads presentation (PKP Youtube) - Traveling to Belgium for OASPA and OSS ORE meetings - Working on preprint workflow in OJS - Made a simple [upgrade video](https://www.youtube.com/watch?v=twTfYLVSPrI) -- went through upgrade documentation in the process - Michael (hosting) would like to take a first review, then this group to re-review - Docker docs are welcome/wanted! Agenda ------ - review quick updates - Alec proposal re: helping DIG with the technical documentation - LTS page check in - Two pieces needed: page in PKP wordpress, and image generator in docs hub. Image generator requires new docs hub environment; Erik working towards this. - Updates from the OJS-on-a-pi group - It's working! Recipe shared in Mattermost. - Performance testing will 100% be testing just the MicroSD. - Next steps: set up HostAP for running its own wireless network for demo purposes - Feature requests working group with Members' Committee -- rough notes so far https://hackmd.io/@ehopkins/ry1l5Qkjeg Notes ----- Pending work ------------ Next steps in supported versions: - [ ] Alec clarify the license on web-php. (done: https://github.com/php/web-php/issues/1280) Next steps about [KM tool](https://github.com/pkp/technical-committee/blob/main/meeting-minutes/2024-07-18.md): - [ ] Group to try various proofs of concept: - [ ] AI / chatbot options (Martin) - [ ] FAQ specialized tools (Marc) - [ ] FAQ area in forum for guiding support / Github Discussions for policies (Alec) Old Business ------------ Other topics ------------ - :one: (In progress) How to show OxS requirements?: php version, php plugins, HW requirements... - :two: Core vs. Plugin-Approaches for new features. - :three: Open Repositories integrations (SignPosting, FAIRiCat, COARNotify). - :four: Ideas for the Health Check plugin. - :five: Research integrity checks (e.g., looking for papermills, suspicious activies (author and reviewer being the same person), fast journal turnaround (peer review happening too quickly) - :six: long-term handling of personal data (GDPR, right to be forgotten, user accounts, anonymization of reviewer data vs. data requirements for open peer review) Next Meeting ------------ Third Thursday of the month: **NEW** 7am Vancouver time A note on note taking ----------- Note taking is shared -- anyone may edit the document. Alec will upload to the minutes page 24 hours after the meeting to allow for any final edits or updates committee members have. ******************************* -------- # Thursday 21 August In Attendance ------------- - Present: Alex, Ronald, AJ, Sebastian, Davin, Marc - Regrets: Emily (vacation), Alec, Joey, Martin (vacation), Dulip Meeting at: [Former notes archive](https://github.com/pkp/technical-committee/tree/main/meeting-minutes). Quick Updates ------------- ### What have you been working on lately? - **Alex** - Upgrading OPS to v3.4; - Developing a plugin (with Lepidus) to transfer submissions from OPS to ScholarOne. - **Dulip** - **Sebastian** - Aggregating Feedback for Individualize-Theme(https://github.com/NateWr/individualizeTheme) --> Preparing Upgrade Project Proposal - To be included in the gallery soon (and some documentation addition about how to get a plugin in the gallery might be helpful) - Finishing Initial Evaluation of Automatic OJS Tests - **Marc** - Vacations mode, but... - Preparing a talk about Docker for CRAFT-OA. - Docker images improvements (with Jon and Andrew). See [here](https://github.com/pkp/containers). - **Davin** - Updated tech workplan for Coalition Publica (CP), including a dedicated OJS CP plugin that would help our support team troubleshoot an OJS instance that we don't administrate (the initial "[HealthCheck plugin](https://github.com/asmecher/healthCheck/)" idea) - **AJ** - Note! I am in my car driving for the first 15 minutes! - OJS/OMP test upgrades - CRAFT-OA work for Datacitations and Controlled Vocabularies - CRAFT-OA meet the experts workshop planning with Ronald - Preparing our OJS/OMP Editors' day https://tsv.fi/fi/uutiset/teemapaiva-open-journal-systems-ja-open-monograph-press-jarjestelmia-kayttaville-0 (In Finnish) - **Ronald** - vacation - CRAFT-OA meet the experts workshop planning with AJ - journal support buisness as usual -------- Agenda ------ - review quick updates ~~ - LTS page -- version chart? (Emily has checked in with Alejandra again too about timeline and location for the page -- there was a feedback deadline that passed without Alejandra hearing anything, but she's going to follow up and report back) ~~ - Updates from the OJS-on-a-pi group ~~ - followup on minimal OxS requirements -- is OJS-on-a-pi all we want to do for now? Are there other benchmarking projects or similar we want to be involved in? Can we remove this topic from our list or change it into getting updates about OJS-on-a-pi rather than general discussion? ~~ After reviewing the various options and with PKP absent from the meeting, those present decided to have an informal talk about topics :four: (Technical Healthcheck) and :five: (Research integrity). Notes ----- - Ronald suggest to distinguish at least two types of health checks - checks following an upgrade process - checks under normal working conditions (test for changes of certain settings, e.g. plugins) - For tech checks (topic 4), Marc suggest: - DB integrity (indexes, duplicates, inconsistencies...). - Folders permissions. - URL endpoints (htaccess mess). - Requirements (php, libraries...). - Versions & security patches. - AJ likes to include perfomance checks. - DB slow query log would be possible but independent, OJS based approach would be more suitable - Maybe it could make sense to check how _known_ problematic queries perform on your site/installation? - Alex talks about topic 5 and recalls PFL (Publications Facts Label) is a good basis. - Also comments that non-technical administrative users have difficulties in finding potential PHP errors, so would it make sense to offer easier acess to the error logs in the "Health Check" plugin? - Davin explains how all this "health check" started. It was a plugin for Editors to show the technical health of the journal. It was not thought as a "pre-flight" list to check before opening your journal to the world (ie: indexing in crossref). - Reference to Plugin of Alec from PKP Sprint (https://github.com/asmecher/healthCheck) - Marc recalls about the DISCO plugin (https://github.com/munipress/disco/) (fits on topic 5) - AJ talks about Dulip's work on checks before publishing (at article level). - Ronald see different check categories: - Publication data: should be run in the moment you publish (article level). - Technical checks. - Journal's quality state. - ... - Marc sees two main categories (tech and content) that could be subcategorized in a lot of ways (Tech: db, performance, urls... Content: journal, article...) depending on the goals of the check. - We agreed in thinking the checks form the user's perspective. Existing projects are: - Erudit: Tech checks for editors to report the support team. - DISCO: Diamond OA journals content (EDCH). - ... - AJ says having a page that lists the most usually required environment information and recent high level errors could help when reportin things to the forum. - showing the last 10 or so error messages could be an approach. - Who will develop and maintain those plugins? - Tech checks looks like a great tool to be used to help reporting in the support forum. It could be extended with log errors and extra information (php version, libraries...) to help editors reporting better when they ask for support. Pending work ------------ Next steps in supported versions: - [ ] Alec clarify the license on web-php. (Filed: https://github.com/php/web-php/issues/1280) Next steps about [KM tool](https://github.com/pkp/technical-committee/blob/main/meeting-minutes/2024-07-18.md): - [ ] Group to try various proofs of concept: - [ ] AI / chatbot options (Martin) - [ ] FAQ specialized tools (Marc) - [ ] FAQ area in forum for guiding support / Github Discussions for policies (Alec) Old Business ------------ Other topics ------------ - :one: (In progress) How to show OxS requirements?: php version, php plugins, HW requirements... - :two: Core vs. Plugin-Approaches for new features. - :three: Open Repositories integrations (SignPosting, FAIRiCat, COARNotify). - :four: Ideas for the Health Check plugin. - :five: Research integrity checks (e.g., looking for papermills, suspicious activies (author and reviewer being the same person), fast journal turnaround (peer review happening too quickly) Next Meeting ------------ Third Thursday of the month: 8am Vancouver time A note on note taking ----------- Note taking is shared -- anyone may edit the document. Alec will upload to the minutes page 24 hours after the meeting to allow for any final edits or updates committee members have. ******************************* -------- # Thursday 17 July In Attendance ------------- - Present: Martin, Dulip (with interruptions), Alex, Marc, Emily, Sebastian, Joey - Regrets: Alec (vacacions), AJ (vacacions) Meeting at: [Former notes archive](https://github.com/pkp/technical-committee/tree/main/meeting-minutes). Quick Updates ------------- ### What have you been working on lately? - **Alex** - Vacation :) - Released a plugin (with Lepidus) to show embedded PDF on the Galleys tab (https://github.com/lepidus/pdfEmbedViewer). - Installed today "DEIA Survey" plugin for SciELO Brazil journals (https://github.com/lepidus/deiaSurvey) -- it should be available on the plugin gallery soon (pending approval from PKP) - Developing a plugin (with Lepidus) to integrate OPS to ScholarOne in order to quickly submit approved preprints to journals using ScholarOne. - **Dulip** - XML Workflows - https://github.com/withanage/doi2jats : Tool for creating jats-references using crossref and openalex as a basis for a OJS plugin. - Evaluation of 3-rd party editors for integration into OJS XML workflows. - **Sebastian** - Developed Testcases for OJS (3.3) for automatic end2end function tests with https://forum.pkp.sfu.ca/t/austausch-zu-automatisierten-tests-fur-ojs/95072/18 - Collecting further requirements for improvements on https://github.com/NateWr/individualizeTheme - Testing Theme and Plugins on 3.5 - Learning Plugin-Dev for Vue.js - **Marc** - Docker images improvements and releases (for OJS and OMP). - CRAFT-OA toolkit writing (almost finished). - Potential grant to implement the OMP-Odoo bridge (coordination with zoe and Thoth). - **Martin** - OJS 3.4.0-9 update of two platforms - Go-live of "Proceedings of the Collegium Helveticum" (joint institute of ETHZ, UZH, zhdk) - Extension of Crossref export to various Crossref record types https://www.crossref.org/documentation/schema-library/markup-guide-record-types/ . Mapping of COAR resource types (OpenAIRE) to Crossref record types. Work in progress, https://github.com/mpbraendle/crossref-ojs. Already in production: posted content, reports - Helping my colleague in transition of UZH HOPE journals to OpenID login with MFA only. ORCID and Switch EduID as IdPs. This due to a CISO regulation that all public UZH platforms must have MFA enabled for login/registration. - Finished retrodigitisation (1947-1989) of a chemistry journal. Poster about process on https://doi.org/10.5281/zenodo.15168440 - Perplexity AI user interaction with articles leads to high download counts of articles, resulting in a distortion of statistics. - **Emily** - currently co-instructor for the current ALA Repositories course - ongoing testing of our new OJS setup for more journals - helping with the new Library Freedom Journal, run on OJS https://ojs.library.queensu.ca/index.php/lfj/index - **Joey** - Assisting with some research on archival/preservation options for OJS journals - Applying to "[1st Canadian Conference for Open Science and Scholarship](https://oscanada.github.io/en/call-for-contributions)" Agenda ------ - review quick updates - August meeting logistics follow up - Interest in co-working group with Members' Committee on feature requests? - Any update on sprint reports re: front-end tech? Reports from Jarda (and Rob from Ubiquity and others) were specifically mentioned last time - Welcome to special guest Jarda so we can discuss the tech stack for reader UI - Follow up on ongoing work - LTS page -- todo re: php license? - any updates from minimal hardware requirements and/or benchmarking for documentation project Notes ----- - There will be an August meeting at the usual time, Marc will chair it - Alex and Marc both expressed interest in participating in a group with Members' Committee to discuss feature requests; Emily will follow up with Sonya about assembling this group - Presentation from Jarda: https://docs.google.com/presentation/d/1x7WCeUKqs2xd_799Cm2avbPlC6cc6n4JUBiWhUCu8jQ/edit?usp=sharing - There was a fair amount of discussion including concerns around node.js but overall the group seems in favour of Jarda's current proposal Pending work ------------ Next steps in supported versions: - [ ] Alec clarify the license on web-php. Next steps about [KM tool](https://github.com/pkp/technical-committee/blob/main/meeting-minutes/2024-07-18.md): - [ ] Group to try various proofs of concept: - [ ] AI / chatbot options (Martin) - [ ] Tools identified above (Marc) - [ ] FAQ area in forum for guiding support / Github Discussions for policies (Alec) Old Business ------------ Other topics ------------ - :one: (In progress) How to show OxS requirements?: php version, php plugins, HW requirements... - :two: Core vs. Plugin-Approaches for new features. - :three: Open Repositories integrations (SignPosting, FAIRiCat, COARNotify). - :four: Ideas for the Health Check plugin. - :five: Research integrity checks (e.g., looking for papermills, suspicious activies (author and reviewer being the same person), fast journal turnaround (peer review happening too quickly) Next Meeting ------------ Third Thursday of the month: 8am Vancouver time A note on note taking ----------- Note taking is shared -- anyone may edit the document. Alec will upload to the minutes page 24 hours after the meeting to allow for any final edits or updates committee members have. ******************************* -------- # Thursday 19 June In Attendance ------------- - Present: Emily, Marc, Sebastian, Ronald, AJ, Alec - Regrets: Joey, Martin, Davin, Dulip, Alex Meeting at: [Former notes archive](https://github.com/pkp/technical-committee/tree/main/meeting-minutes). Quick Updates ------------- ### What have you been working on lately? - **AJ** - **Alec** - OJS/OMP/OPS 3.5.0 out! - OSS ORE M10 deliverable complete - Catching up on lots of pending work. - **Alex** - **Sebastian** - Developing Test Cases for automated Function testing on live instances with German-speaking OJS Group /w Ronald (evaluating Hurl, Cypress and Playwright) - Preparing Presentation of Theme Plugin for OA-Tage (Open Access Days) Conference in September - **Ronald** - Lots of XML-business - plugin upgrades - DE journal hosting network established: https://open-access.network/vernetzen/digitale-fokusgruppen/fokusgruppe-ojs-hosting - **Marc** - Docker images: [Looking for feedback](https://forum.pkp.sfu.ca/t/omp-docker-images-for-3-3-0-21-3-4-0-9-and-3-5-0-0/96103). - OMP is now up to date (3.3, 3.4 and 3.5) and OJS 3.5 was also released. - Relevant changes: multi-stage, debian based, php8.3, OMP & OJS scripts convergence, postgres support, bugfixing. Talking in the "containers" channel. - Exploring an Odoo-OMP integration. Anyone interested in the topic? - OMP 3.3.0-16 upgrade to 3.3-LTS. - CRAFT-OA toolkit writing. - EDCH Forum & Register external review. - **Martin** - **Emily** - working on test site for our expanded journal hosting service at USask Agenda ------ - Brief review of some survey responses (also these are FLOSS mascots since a lot of you were not familiar and they are fun! https://en.wikipedia.org/wiki/List_of_computing_mascots) - mascot list missing: steam locomotive - Relationship to PKP: vital, shapes software behaviour, we have a lot of freedom and support; we should provide technical advice and practical know-how for long-term strategic planning and advance smaller topics through work groups - Goals for this year: integrating XML features, handling 'Feature Requests' forum (Feature requests could be a good opportunity to have a working group with people from Membership Committee) - Highlights from past work: coming out with LTS versions, pre-release testing, involvement in OJS Community Development Priority Survey (could be good to work with Comms team to communicate back how many of these priorities have been realized in 3.5) - New/priority topics: Core vs. Plugin, help for plugin developers, Research Integrity checks - (as needed) any followup from AGM which is on Tuesday 17 June -- register here: https://pkp.sfu.ca/2025/05/20/pkp-2025-agm-registration-open/ and here is the annual report: https://pkp.sfu.ca/2025/06/16/annual-report-2024-release/ - Follow up on ongoing work (LTS page, OxS requirements) - ~~Welcome to special guest Jarda so we can discuss the tech stack for reader UI~~[postponed until July] - Reports/follow up from the sprint Notes ----- - Alec show us a test of tiptap integration in OJS. Looks promising. - LTS page? - Alec working on the supported versions chart (based on web-php repo) - Alec needs to clarify that the license on web-php allows us to do this - TC has been in touch with Alejandra. - Need better clarity / broader communication of dates e.g. for deprecation of last LTS. Alec to include TC representation in release process debrief -- that'll include e.g. PKP comms team. - OxS requirements? - README.md now includes software requirements - Hardware requirements - TODO: Provide example platform and benchmark information. Alec working on this as part of OSS ORE project. - The group could develop the test specifications to help -- e.g. use [siege](https://github.com/JoeDog/siege) with X options on Y URLs - Discussion: Could the beacon be extended to reveal platform information? (Telemetry is controversial and we've been quite careful!) - Alec: Rather than trying to add a telemetry back-channel, which would be controversial, we're trying to push the use/adoption/support of open science principles, which can achieve the same aim. This won't tell us e.g. what plugins are used, but will possibly expose workflow info. - Fun idea: what about smallest-possible-OJS (e.g. Raspi)? - Totally possible! - Discussion: What about additional optional components that might have higher requirements? - Alec: We're working hard on keeping this from adding to requirements unless really necessary. Example: Vivliostyle in the browser rather than server-side. - Alec and Sebastian to work on this. - Alec: Watch for sprint reports on the future of front-end technology. Jarda (and Rob from Ubiquity and others) have a good plan going forward. Pending work ------------ Next steps in supprted versions: - [ ] Alec clarify the license on web-php. Next steps about [KM tool](https://github.com/pkp/technical-committee/blob/main/meeting-minutes/2024-07-18.md): - [ ] Group to try various proofs of concept: - [ ] AI / chatbot options (Martin) - [ ] Tools identified above (Marc) - [ ] FAQ area in forum for guiding support / Github Discussions for policies (Alec) - We are using the "FAQ" tag: https://forum.pkp.sfu.ca/tag/faq - [x] Alec to let Roger / support forum folks know that we're looking at options [done] Old Business ------------ Other topics ------------ - :one: (In progress) How to show OxS requirements?: php version, php plugins, HW requirements... - :two: Core vs. Plugin-Approaches for new features. - :three: Open Repositories integrations (SignPosting, FAIRiCat, COARNotify). - :four: Ideas for the Health Check plugin. - :five: Research integrity checks (e.g., looking for papermills, suspicious activies (author and reviewer being the same person), fast journal turnaround (peer review happening too quickly) Next Meeting ------------ Third Thursday of the month: 8am Vancouver time A note on note taking ----------- Note taking is shared -- anyone may edit the document. Alec will upload to the minutes page 24 hours after the meeting to allow for any final edits or updates committee members have. ********************************* ********************************** -------- # Thursday 17 April In Attendance ------------- - Present: Alex, Sebastian, Alec, Joey, Marc, AJ, Ronald, Emily - Regrets: Meeting at: [Former notes archive](https://github.com/pkp/technical-committee/tree/main/meeting-minutes). Quick Updates ------------- ### What have you been working on lately? - **AJ** - Preliminary work for Data Citations support - Testing OMP Crossref plugin, got some help from Spain (not Marc) - Doing some mass imports to OMP with a modified tsvConverter script - Looking into upgrading the Funding plugin - **Martin Brändle** - Meetings (German speaking working group) on automated testing. - Shifted Lucene indexing to a remote Solr test server. - Swiss Diamond OA Workshop 21th March 2025 (poster, workshop contribution). - Retrodigitisation (1947-1989) of a chemistry journal, ongoing. - Test update of a OJS 3.4 multi-journal installation to OJS 3.5.0 RC2. * **Alex** - Gearing up to install Demographics Question Plugin (developed by Lepidus) to SciELO journals (https://github.com/lepidus/demographicData/) - Upgrading OPS to v3.4 - Upgrading other OJS installs to v3.4 - Improvements to the Dataverse plugin (with Lepidus) - **Sebastian** - Trying to implement public statistics on journal pages (Plan S compliance) - **Ronald** - Working on plugin upgrades for 3.5 * **Alec** - 3.5.0-0 due in probably a couple of weeks - Seeing increased activity of scripted attacks on older OJS/OMP/OPS installs - **Marc** - Helping with a 2.x to 3.3 upgrade. - During the task I created [this repo](https://github.com/marcbria/ojsExtraTools) with helper tools. - Working with fellows that like to extend the openID plugin. Agenda ------ - Thank you Marc! :trophy: :confetti_ball: - Housekeeping - Membership renewals April 1: please email me (emily.hopkins@usask.ca) to confirm you would like to renew your term if it has been two years!) - Question of the month: special survey edition (see below) - Brief review of existing topics list (see below for proposed changes based on chat) - Review and approve Supported Versions page from working group so we can hand off to PKP Comms: https://hackmd.io/@ehopkins/HJRqMy56ke/edit - Topic: How to show OxS requirements?: php version, php plugins, HW requirements... https://github.com/pkp/pkp-lib/discussions/9559 Notes ----- ### Supported Versions page - Q: Distinctions between maintenance, support, etc? - A: PKP goes right to maintenance from release. - Q: What about adding upgrade support to graph -- e.g. what the earliest version you can upgrade from for a new release? - A: Maybe not -- if we can get folks onto a clear upgrade track (LTS or STS), then it becomes unnecessary. - Q: What about backwards compatibility? - A: We don't offer "backwards compatibility" *per se* -- but there are two docs for orienting users who upgrade: - What's New in 3.4: https://docs.pkp.sfu.ca/learning-ojs/en/about-ojs#whats-new - Release Notebook for 3.4: https://docs.pkp.sfu.ca/dev/release-notebooks/en/3.4-release-notebook - Q: What about documentation for folks who go right from 3.3 to 3.5? - A: We don't have specific documentation for that jump. - Alec: Suggest that we add "what I need to know about 3.3 to 3.4" for those who are going right from 3.3 to 3.5. - Added to 3.5.0 Release Notebook; will suggest adding to 3.5.0 documentation as well. Alec will ping Emma. - Q: Where are we duplicating documentation that will need to be updated? Can some of it be removed? - A: It'll be a mix: Docs hub, maybe github/codebase, also PKP website. No one team manages all of these, so we'll need to bring in several groups to check coverage. - Marc: Suggests to centralize information to avoid unsyncronizations. Also suggests a check of the additional pages talking about this same topic that could be outdated (and decide to close or update accordingly). - First research of associated pages: https://hackmd.io/Ls58u1HaTeGuhnntEYQX-w?view#References - Probably TC can help in the mapping or detecting inconsistencies. - Next steps: This group to review and approve in principle - Alec (and dev team) to review specifics e.g. dates - Alec to experiment with PHP-side graphic generation tool based on [what's used on the PHP website](https://github.com/php/web-php/blob/77d8a8c8f0b5072c7d2e58284eedf6871baf52ea/images/supported-versions.php) - Then, Emily to take to Alejandra (e.g. on Tech Committee Mattermost channel, which is open) - PKP-Coms will decide exactly where to put it (and this will decide some technical aspects of how it's written). ### How to show OxS requirements? Like php version, php plugins, HW requirements... https://github.com/pkp/pkp-lib/discussions/9559 - PKP suggests use the composer.json to get this information. - Needs work to ensure that the checks are run/documented in the right place: - Maybe document what Composer script needs to be run to check deployment? - Maybe built the checks right into the install/upgrade process? - Q: What about Ansible / Playbook style deployments? - Could we refer to the Composer document listing modules? - Would this be confusing for admins who don't work with Composer? - Q: What about hardware requirements? - Alec: It's very hard to give firm requirements. What we can do is perform benchmarking and document the conditions. Will need to do this for OSS ORE project. We agreed in continue with this topic in next meeting. Pending work ------------ Next steps about [KM tool](https://github.com/pkp/technical-committee/blob/main/meeting-minutes/2024-07-18.md): - [ ] Group to try various proofs of concept: - [ ] AI / chatbot options (Martin) - [ ] Tools identified above (Marc) - [ ] FAQ area in forum for guiding support / Github Discussions for policies (Alec) - We are using the "FAQ" tag: https://forum.pkp.sfu.ca/tag/faq - [x] Alec to let Roger / support forum folks know that we're looking at options [done] ### Question of the month For this month I am going to take over this section with a little survey. Answer as many as you like, I appreciate it very much. I will email them to you so you can reply directly, then summarize some responses for us to review in May and use for planning: 1. How do you see this group's role in relation to the rest of PKP? 2. What is one thing you are really hoping we will do in the next year? 3. Please tell me a about a highlight of your experience with this group so far -- maybe a project or decision you were glad to be involved with, or something else you like. 4. Please suggest a new topic for the list, or highlight an existing topic you want us to prioritize. 5. What is your favourite FLOSS mascot? Feel free to add questions you might like us to ponder in the future below: * Question: Old Business ------------ - :one: API patterns: Jarda is asking for feedback. - remove? no one voted for it or mentioned it... - :two: OMP dev priorities: If you could make a small development for OMP, what would it be? - remove: Zoe already did it - :three: Version and Support communication page: What to show? General rules? Example - remove: working group drafted the page and will approve and hand off to PKP Comms after today's meeting - :four: Ideas for the Health Check plugin. - keep! - :five: Contextual help in OxS: Missing oportunity? Improve or abandon it? - remove...? Seems like PKP has already moved on but if you want us to prioritize this include it in your survey :smiley: - :six: Open Repositories integrations (SignPosting, FAIRiCat, COARNotify). - keep - :seven: GDPR documentation. - remove: outdated, covered by CRAFT OA - :eight: How to show OxS requirements?: php version, php plugins, HW requirements... - keep, we will discuss it today - :nine: Let's talk together :three: and :eight: - remove since :three: was dealt with separately - :one::zero: Core vs. Plugin-Approaches for new features. - keep Other topics ------------ TBD Next Meeting ------------ Third Thursday of the month: 8am Vancouver time A note on note taking ----------- Note taking is shared -- anyone may edit the document. Alec will upload to the minutes page 24 hours after the meeting to allow for any final edits or updates committee members have.

Syntax	Example	Reference
# Header	Header	基本排版
- Unordered List	Unordered List
1. Ordered List	Ordered List
- [ ] Todo List	Todo List
> Blockquote	Blockquote
Bold font	Bold font
Italics font	Italics font
~~Strikethrough~~	~~Strikethrough~~
19^th^	19^th
H~2~O	H₂O
++Inserted text++	Inserted text
==Marked text==	Marked text
[link text](https:// "title")	Link
![image alt](https:// "title")	Image
`Code`	`Code`	在筆記中貼入程式碼
```javascript var i = 0; ```	`var i = 0;`
:smile:		Emoji list
{%youtube youtube_id %}	Externals
$L^aT_eX$	L^aT_eX
:::info This is a alert area. :::	This is a alert area.