add meeting minutes to 2025-05-20 meeting (#49)

Author: sergegoussev

project-content/meeting-minutes.md

@@ -142,4 +142,19 @@ This document summarizes the meetings of the workstream
 -   The team discussed and endorsed the about team page, similar to how [the Turing way records contributors](https://book.the-turing-way.org/afterword/contributors-record). Action item for the team is either to contribute to the page directly via PR (see CONTRIBUTING) or coordinate offline.
 -   How this guide and the interim catalogue will be presented next week was discussed and approved
 -   For academic material, the group discussed possible guidance. Initial thoughts of the group was that while code can be in GitHub and follow compendium type structure, datasets do not need to be registered if they are small training datasets and could just be version controlled in GitHub directly. The policies of the university should take precedence.
--   The group agreed to switch to a 3 week cadence with the next meeting three weeks after the conference.
+-   The group agreed to switch to a 3 week cadence with the next meeting three weeks after the conference.
+
+## 2025-05-20
+
+### Agenda
+
+-   Discuss OKR based slight restructure of the charter to clarify the direction.
+-   Discuss what to recommend as guidance in the call out email when the Ottawa Group organizers do a call for papers
+-   Discuss backlog of items to prioritize work for the year (did not finish)
+
+### Notes
+
+-   The team discussed and approved the proposed [OKR based](https://www.whatmatters.com/faqs/okr-meaning-definition-example) restructure of the project charter. Key points included how to include administrative activities that aim to disseminate knowledge about the project/our guidance. Final charter and structured milestones can be mocked up and presented at the subsequent meeting.
+-   The team discussed how training (provided by workstream 3) could support the project. A notable example was RAP principles, which can be taught in a general way and options to apply them to either research or production could be given at the end. A process flow may also be applicable to support individuals knowing how to open their projects.
+-   The team discussed the difference between a researcher developing a new method (in which case open data is best) or a researcher is applying a tried method on their internal data (in which case use of proprietary data is absolutely fine).
+-   Team to add PR directly or email Serge to add their contact info to the [Project team members](https://un-task-team-for-scanner-data.github.io/reproducibility-project/docs/about.html#project-team-members) section.