Warning: This page has not been updated in over over a year and may be outdated or deprecated.
community:pmc_meetings:minutes20230213
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
community:pmc_meetings:minutes20230213 [2023/02/13 16:00] – [Other Items] demiankatz | community:pmc_meetings:minutes20230213 [2023/03/13 13:35] (current) – [8. Fundraising Communication Plan] demiankatz | ||
---|---|---|---|
Line 3: | Line 3: | ||
Attending: Anne Christensen, | Attending: Anne Christensen, | ||
- | Apologies: Oliver Goldschmidt, | + | Apologies: Oliver Goldschmidt, |
- | + | ||
- | :!: This document currently serves as an agenda but will be converted to minutes following the meeting. | + | |
===== 1. Review of Action Items from Previous Meeting ===== | ===== 1. Review of Action Items from Previous Meeting ===== | ||
Line 27: | Line 25: | ||
* The newsletter should clarify which future release(s) will include completed work. Demian will start doing this going forward. | * 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, | * No one seems to use or care about the autogenerated PHPDocumentor documentation, | ||
- | * David/Ere agreed that there' | + | * David/Ere agreed that there' |
* 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? | * 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? | ||
* Ere asked whether we need version-specific pages in some cases? Can we use a struct plugin to control this in a more structured way? André asked if we should consider snapshotting versions of the wiki at points in time to refer to specific versions? (If so, how do we document upcoming features?). Alternative proposal from Demian: simply state that documentation should be accurate for some number of recent VuFind releases (e.g. latest 2-3 major releases). Older notes could be removed. Since VuFind is designed to be fairly evergreen, this might be a more maintainable solution, and encourage people to upgrade from very old versions while still leaving likelihood of most documentation still applying to older versions. Mohan highlighted the need to upgrade documentation relating to VuFind' | * Ere asked whether we need version-specific pages in some cases? Can we use a struct plugin to control this in a more structured way? André asked if we should consider snapshotting versions of the wiki at points in time to refer to specific versions? (If so, how do we document upcoming features?). Alternative proposal from Demian: simply state that documentation should be accurate for some number of recent VuFind releases (e.g. latest 2-3 major releases). Older notes could be removed. Since VuFind is designed to be fairly evergreen, this might be a more maintainable solution, and encourage people to upgrade from very old versions while still leaving likelihood of most documentation still applying to older versions. Mohan highlighted the need to upgrade documentation relating to VuFind' | ||
Line 49: | Line 47: | ||
===== 3. Conflict of Interest Policy ===== | ===== 3. Conflict of Interest Policy ===== | ||
+ | |||
+ | Demian is still waiting for a couple more submissions but expects them soon. | ||
===== 4. Translation Platform ===== | ===== 4. Translation Platform ===== | ||
+ | |||
+ | André is still working on this. He will make a determination by Friday, 2/17, whether we should use the new translation platform for the 9.0 release translation cycle, or if we should continue to do things "the old way" for one more release before attempting to transition. | ||
===== 5. Registered Service Provider Update ===== | ===== 5. Registered Service Provider Update ===== | ||
Line 83: | Line 85: | ||
Next planned " | Next planned " | ||
- | See [[community_call:minutes20221206|December | + | See [[community:pmc_meetings: |
===== 9. Possible Future Actions ===== | ===== 9. Possible Future Actions ===== | ||
Line 94: | Line 96: | ||
* Marketing project (better VuFind® definition, website improvements, | * Marketing project (better VuFind® definition, website improvements, | ||
* Publication / presentation efforts related to PMC and sustainability | * Publication / presentation efforts related to PMC and sustainability | ||
- | * Look at [[https://wiki.lyrasis.org/ | + | * Look at [[https://itav.lyrasis.org/ |
- | * Look at [[https://wiki.lyrasis.org/ | + | * Look at [[https://itav.lyrasis.org/ |
===== Other Items ===== | ===== Other Items ===== | ||
Line 112: | Line 114: | ||
===== Action Items ===== | ===== Action Items ===== | ||
+ | * ALL: submit signed Conflict of Interest policy acknowledgments to Demian for submission to the OLF (if you haven' | ||
+ | * ALL: consider whether to renew for a second PMC term when our two year anniversary arrives in April, 2023. | ||
+ | * Demian/ | ||
+ | * André/ | ||
+ | * André: investigate potential costs of a security audit. | ||
+ | * Demian: Schedule a meeting to discuss training/ | ||
+ | * Chris/ | ||
+ | * Demian: Work with Susan to begin an inventory of wiki content (outdated pages, references to old versions, etc.) | ||
+ | * Any interested parties: Begin research to improve or replace PHP_CodeSniffer, | ||
+ | * Demian/ | ||
+ | * ALL: Think about documentation improvements for further discussion next time. | ||
+ | * ALL: Think about whether/how to participate in WOLFcon 2023. | ||
+ | * Demian: include " | ||
+ | * Demian: include documentation on a future Community Call agenda for further discussion. | ||
---- struct data ---- | ---- struct data ---- |
community/pmc_meetings/minutes20230213.1676304051.txt.gz · Last modified: 2023/02/13 16:00 by demiankatz