# April 10, 2025 Advisory Committee

**URL:** <https://forum.openrefine.org/t/april-10-2025-advisory-committee/2230>\
**Category:** Day-to-day project operations\
**Tags:** minute-advisory\
**Created:** [April 10, 2025, 8:57pm UTC](https://forum.openrefine.org/t/april-10-2025-advisory-committee/2230 "2025-04-10T20:57:51Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Martin](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/martin/32/7_2.png) [@Martin](https://forum.openrefine.org/u/Martin)\
**Post date:** [April 10, 2025, 8:57pm UTC](https://forum.openrefine.org/t/april-10-2025-advisory-committee/2230/1 "2025-04-10T20:57:51Z")

</div>

## Attendees

- Esther Jackson - Advisory Committee
- Jan Ainali - Advisory Committee
- Martin Magdinier - Project Manager

## Discussions

### Wikimedia group

The group reviewed the progress regarding [Creating an OpenRefine Wikimedia Group](https://forum.openrefine.org/t/creating-an-openrefine-wikimedia-group/2132)  
Esther and Jan are looking to identify a second contact who is not a member of the Advisory Committee. Esther will reach out to potential candidates. The next step will be to draft the application, which will be coordinated in the same forum post.

### Rory progress

Martin provided an update regarding Rory's progress.

- Rory and Martin have a 30-minutes check weekly on Thursday.
- His contract is renewed until Oct 31, 2025.
- Martin is planning a trip for Rory to come to Quebec in the coming weeks to meet in person with another community member.
- Rory is ramping up in responsibility to review and merge PR. He is also currently [Releasing 3.9.3](https://forum.openrefine.org/t/releasing-3-9-3/2219)

### Update on governance

Martin presented the latest update on the governance PR:

> <https://github.com/OpenRefine/OpenRefine/pull/7023>
>
> This PR follows discussions on \[the forum\](https://forum.openrefine.org/t/improv…ing-transparency-advisory-committees-role-and-community-involvement/1672/37). The goal is to document how the project currently operates. 
> 
> \## What changed
> As discussed I
> \- Added Apache meritocratic model back
> \- Clarified the process for voting new members into the different role 
> \- Clarified how funds are managed. 
> \- Introduced the Core Developer Group 
> \- Remove the Steering Committee
> 
> I also took the opportunity to introduce the following role
> \- Clarify language in the Code of Conduct
> \- Code of conduct committee
> \- Designer 
> 
> \## What will be updated in a second phase
> \* I left the Project Manager description as-is. The new scope is currently being discussed with the Advisory Committee. 
> \* I have documented the current process for renewing the Advisory Committee. Once we finalize the process, I propose we update the Governance to make it more transparent.
> \* Mention the mission, vision, and values. We need to add them first on the website and reference them in the Governance and Code of Conduct document.

The group discussed whether the _Election_ section should be categorized under Policies or Governance. The group reached a consensus to place it under Governance. Martin will do the update. Additionally, Martin created the #election tag in the forum to consolidate related discussions.

Martin plans to keep the PR open for feedback until the end of the month.

### Goalpost update

Martin presented the PR with a plan to merge it next week

> <https://github.com/OpenRefine/openrefine.org/pull/445>
>
> The current list of goal posts has been compiled from the \[2024 survey edition\](…https://forum.openrefine.org/t/results-from-the-feature-prioritization-survey-2024/1847) and enriched from \[other items shared on the forum and wiki\](https://forum.openrefine.org/t/openrefine-2024-barcamp-strategizing-openrefine-roadmap/1633/2). This effort is part of the \[contributor handbook creation\](https://forum.openrefine.org/t/requesting-feedback-documenting-openrefine-community-handbooks/1224/12) and \[advertised here\](https://forum.openrefine.org/t/march-20-2025-advisory-committee-only/2170).
> 
> \*\*Suggestion\*\*: 
> \* To make the list more digestible, we can group items on \`goal-post.md\` by status rather than creating a long list. 
> \* I am open to change the list of \`status\` and their definition. I made a judgment call for each one based on available information. 
> 
> \*\*To Do\*\*
> 
> \- \[x\] The Extension Idea page replaces the current wiki: https://github.com/OpenRefine/OpenRefine/wiki/Extension-ideas. It should be deleted after this PR is merged.

### Fundraising

Martin started to draft outreached emails to the following organizations.

- The Navigation Fund
- Futo
- Smidt Science

Next

- Martin asked the Advisory Committee to review the outreach emails for feedback.
- Martin is meeting with Danielle on Friday, April 11, to finalize them.
- Martin will start the outreach next Monday.
- Martin will also email community members in the UK who may qualify for the [Research Software Maintenance Fund](https://www.software.ac.uk/programmes/research-software-maintenance-fund)
- The application to OTF by Superbloom is now complete. Martin will share it on the forum.

### Fund Allocation

Martin will request a no-cost extension for the EOSS-5 grant. This extension will allow us to reallocate the funds if needed. It's safer to plan for this possibility, even if we accelerate our spending and complete the project by October 31.
