public inbox archive for
 help / color / mirror / Atom feed
From: Stephan Meijer <me-nPKYAObcRdo6Blr+0TYHagC/>
To: pandoc-discuss <pandoc-discuss-/>
Subject: Offering support to mitigate Pandoc's Issue/PR backlog
Date: Mon, 6 Nov 2023 04:37:06 -0800 (PST)	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 1423 bytes --]

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

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

You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/
To view this discussion on the web visit

[-- Attachment #1.2: Type: text/html, Size: 1741 bytes --]

             reply	other threads:[~2023-11-06 12:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 12:37 Stephan Meijer [this message]
     [not found] ` <2cdf2453-8021-43d8-a69b-8b6d3d260374n-/>
2023-11-06 12:47   ` Stephan Meijer
     [not found]     ` <13581e70-a573-414a-ab05-bfa9f73b9259n-/>
2023-11-07  3:09       ` John MacFarlane
2023-11-06 15:31   ` Albert Krewinkel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \
    --to=me-npkyaobcrdo6blr+0tyhagc/ \
    --cc=pandoc-discuss-/ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).