How you can help NiceGUI right now 🙏

[falkoschindler]

First, a thank you: the stream of issues, discussions, and pull requests is a sign of a healthy, engaged community, and we're grateful for it.

We also want to be honest: we're currently behind on reviewing PRs. This isn't because of a flood of tickets — it's a bandwidth thing. A maintainer reviewing every change is the bottleneck, and that step is hard to parallelize by simply adding more open PRs to the pile.

Several of you have generously asked "how can I help?" — so here's a concrete answer. Counterintuitively, the most useful help right now is usually not another feature PR. It's the work around review — the ~80% that doesn't require a maintainer's final say, but that today lands on us by default.

Where you can take real load off us

1. Pre-flight other people's PRs.
Before a maintainer ever looks, a PR can be checked out, run, and stress-tested by anyone:

• Does it actually work? Build a small reproducible example and try it.
• Verify the author's claims — especially "no breaking changes". Compare behavior against main.
• Check it against CONTRIBUTING.md: conventions, tests, docs.

A PR that arrives already exercised and de-risked is dramatically cheaper for us to merge. Leave your findings as a review comment — that's enormously helpful even without merge rights.

2. Help with triage.
Browsing open issues and PRs and adding clarity is real work that frees real time:

• Can you reproduce a reported bug? Note the exact steps (or that you couldn't).
• Is a PR stale, superseded, or already fixed elsewhere? Say so.
• Does an issue lack the info needed to act on it? Ask the reporter the missing questions.

3. Unblock stalled PRs.
Some PRs sit in "changes requested" simply because the author went quiet, and the remaining work is mechanical — a rebase, addressing review comments, a missing test. Picking those up (with the original author's blessing where appropriate) pushes them over the line. Others are stuck on a genuine design decision — for those, see below.

4. Prepare decisions instead of waiting for them.
A few things are irreducibly ours to decide: public API design and what fits the roadmap. But you can make those decisions fast instead of slow — lay out the options, the trade-offs, and any prior art, so the call takes five minutes instead of fifty. A PR description that frames the open questions clearly is a gift.

5. Support the community.
Answering questions in Discussions, helping newcomers, and reproducing bug reports all relieve general bandwidth — even when none of it touches a single line of the codebase.

What this builds toward

This isn't only about clearing a backlog. Help of this kind is how trust grows: the more we see solid judgment on the PRs we do review, the more we can confidently hand over — eventually including ownership of whole subsystems by the people who know them best.

If you're not sure where to start, just ask in the comments and we'll point you at something. Thank you for being here. 💙

[evnchn]

Posted by @evnchn via Claude Code.

@HnBigVolibear @moi90 @falkoschindler — my bad: I should have split this off the moment it stopped being about Falko's PR-review request, instead of letting it grow inline here. I've moved the "official AI skill for NiceGUI" conversation into its own discussion so it doesn't derail this announcement:

👉 #6097

Let's continue there. 🙏