Community contributions and PR timelines

[mcoliver]

Hi everyone,

I’ve been contributing to OpenRV over the past year, and it’s been great to see several PRs merged and moving the project forward.

I’m looking for some guidance to help align my efforts with the project’s current goals. While some PRs move through quickly, I have a few pending that are several months old. Some of these are focused on critical maintenance, such as dependency updates to fix CVEs, performance improvements, and bug fixes. Others fix things that are currently broken with the build as it stands today (e.g., #1176 and #1180 ).

I fully appreciate that the maintainers have limited resources and that rigorous testing is required. To help me contribute more effectively, I’d love to get some clarity on:

Expected Timelines: What is the typical cadence for reviewing community PRs, specifically those involving security, performance, and fixing broken things?

Prioritization: Are there specific areas of the roadmap where community contributions are most needed right now?

My goal is to stay engaged and ensure that the work I’m doing provides the most value to the project. Any advice on how to better navigate the submission process or prioritize my upcoming work would be greatly appreciated.

[compaga]

Hi mcoliver,

First, I would like to thank you for you interest and for your contributions and we really appreciate external contributions. I would like to acknowledge that we currently are struggling with the amount of PR to review and test coming from the community, we are aware of the situation and are trying to find solution.

Last Tuesday, at Open RV TSC meeting, we discussed this specific topic. We have agree to a set of PR labels that should help clarifying the actually "state" for contributors and we are actively working on labelling all PRs. Hopefully, this can give you visibility on priorities. We are looking for more ways to make PR approval faster but the lack of unit-tests and automation is slowing down the process, something we'd also want to improve.

I will also setup time aside to update Open RV roadmap so it will be easier for you to know when you can help.

The TSC meeting is open to everyone (many studios usually join), feel free to join next iteration and introduced yourself, we love to "virtually" meet you. This is a great place to understand and discuss priorities and provide feedback.

Hope this help,

Alain

[mcoliver]

Yeah saw those labels. Love them. Thank you. Thanks for the reply and update. For other people coming across this in the future and looking to join meetings, here is a link to the ASWF Meeting calendar https://zoom-lfx.platform.linuxfoundation.org/meetings/aswf