About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
community:pmc_meetings:minutes20230213

This is an old revision of the document!


PMC Meeting: February 13, 2023

Attending: Anne Christensen, Chris Hallberg, Demian Katz, André Lahmann, Ere Maijala, David Maus, Mohan Raj Pradhan

Apologies: Oliver Goldschmidt, Leila Gonzales, Craig Murdoch

:!: This document currently serves as an agenda but will be converted to minutes following the meeting.

1. Review of Action Items from Previous Meeting

  • ALL: submit signed Conflict of Interest policy acknowledgments to Demian for submission to the OLF (if you haven't already). ONGOING
  • ALL: review/comment on/approve Conflict of Interest changes to governance document: pull request #2653 DONE
  • ALL: consider whether to renew for a second PMC term when our two year anniversary arrives in April, 2023. ONGOING
  • Demian/Mohan: make further progress on updating Koha installation and Open Data Sources wiki pages. ONGOING
  • André/Demian: continue investigation of lokalise platform for i18n. ONGOING
  • Demian: follow up on pending RSP payments. DONE (but some payments still pending)
  • André: investigate potential costs of a security audit. ONGOING
  • Demian: Add David as a GitHub committer. DONE
  • Demian: Schedule a meeting to discuss training/documentation with Mohan and interested RSP representatives. ONGOING (waiting for responses to RSP follow-up)
  • Demian: Send RSP form link to Mohan. DONE
  • Demian: Change email address in Code of Conduct to info@vufind.org. DONE

2. Documentation

The Documentation Survey closed on February 6. The survey revealed a few areas where action may be possible:

  • The newsletter should clarify which future release(s) will include completed work. Demian will start doing this going forward.
  • No one seems to use or care about the autogenerated PHPDocumentor documentation, and there were complaints about the verbosity of the comments that power it (though comments were generally regarded as useful/valuable). This points to the possibility of reviewing our PHP_CodeSniffer rules and possibly changing the way we approach PHPDoc comments, since this has not been reviewed or changed in over a decade, and PHP has significantly evolved (e.g. with typehints built into the language which render many doc comments redundant).
  • References to older versions cause some confusion, and raise concerns about documentation being out of date. Should we remove or rephrase this for versions before a particular threshold?
  • A user requested a sitemap/content map, but the site already has one (Sitemap button at bottom of page). Can we make the sitemap more visible and/or more useful? (Right now it's fairly unreadable/unhelpful since it just uses the short URL names of pages).
  • There were layout-related requests – more whitespace/better layout/more visual content like screen shots. Should we identify some specific pages that would benefit from this and work on reformatting them? Would more general CSS tweaks help?
  • A significant number of respondents indicated that the documentation needs more examples. Are there obvious areas where we should add more?
  • It was suggested that the "Features" page should be updated and expanded – this ties in with the marketing improvements already on our to-do list.
  • There was a request for a “howto” page explaining how to extend code from the VuFindSearch module.
  • There was a request for more context in the changelog; Demian will try to do better on this.
  • Video tutorials seem to be very well-regarded; the Learning VuFind® book has not been used as heavily but has significant positive (and no negative) feedback.

Susan Turkel at Villanova is willing to do some review/editorial work if we define a project for her.

Discussion: Is it worth sharing any of these results (or a summary) on the wiki?

Demian and Mohan continue to collaborate on Koha documentation.

Work is still pending on MeSH, DoAJ, PubMed Central and NepJol “open data sources” pages. Mohan also plans to contribute documentation related to integrating other software packages like SubjectsPlus and Moodle, which also support OAI-PMH.

3. Conflict of Interest Policy

4. Translation Platform

5. Registered Service Provider Update

HealthNet Nepal has joined as our fourth RSP.

Demian is still working on three more pending memberships.

6. WOLFcon 2023

The time/place of WOLFcon 2023 has been tentatively set as August 22-24 in Chicago, IL. We need to determine who can attend, what we will present, and how this should relate to the Summit.

Demian expects that he should be able to attend.

Based on input from Mohan, Demian suggested a panel to discuss grants and collaborative fundraising strategies with other OLF projects.

7. Goals for 2023

Mohan suggested a goal-setting exercise for the PMC, to have a plan for the work of the coming year.

Some possible/likely goals:

  • Release versions 9.0 and 9.1 (April / October?)
  • Run fundraising campaign in parallel with summer conference season
  • Complete a documentation improvement project
  • Complete a website improvement project (marketing-oriented)
  • Finish implementation of standard translation platform
  • Investigate possible training partnerships and fundraising around training materials

8. Fundraising Communication Plan

Next planned “membership drive” – in tandem with next Summit, which in turn will likely be timed around the next WOLFcon.

See December 6, 2022 minutes for brainstorming notes about use of funds.

9. Possible Future Actions

Some other possible items for the future:

Other Items

Action Items

community/pmc_meetings/minutes20230213.1676300733.txt.gz · Last modified: 2023/02/13 15:05 by demiankatz