Our team has been contemplating forking as a way to keep our projects moving along, but we're fully aware of the maintenance challenges this could introduce, especially when it comes to staying in step with the updates from the main Pandoc repository.
We're invested in supporting the Pandoc community and would much prefer to work within the existing framework to get these PRs processed. We're on the lookout for any advice on how to make this as smooth and unobtrusive as possible for everyone involved.
Could you guide us on the best way to move forward with these contributions? Any pointers on how to streamline our PRs or suggestions on alternative approaches that could help lighten the load for the Pandoc maintainers would be much appreciated.

On Monday, 6 November 2023 at 13:37:06 UTC+1 Stephan Meijer wrote:

This is mainly directed to @jgm / John MacFarlane and/or Pandoc maintainers.

I am reaching out on behalf of our team, which frequently utilizes Pandoc for numerous conversion tasks. We have been closely following the project’s progress and have observed the growing number of open issues (947 to date) and pull requests (77 at the current count). Recognizing the immense value that Pandoc provides to the community, we are keen to explore how we might contribute to the project's health and sustainability.

Understanding that managing such a popular project can be challenging, we are curious about the underlying factors contributing to the backlog. Could the project be facing constraints in terms of time, resources, or funding? We are contemplating what actions our team could take to assist effectively.

We are eager to give back to the Pandoc community that has offered us so much. Please let us know the most impactful way we can lend our support.

Stephan Meijer