The state of community contributions in PrimeNG

[Will-Smith-007]

Dear Primetek team,
Dear fellow developers,

This post is about a pattern many PrimeNG users will recognize.

While building a UI you encounter a bug or missing feature in PrimeNG. Then you search for existing issues and PRs which could address your problem. If no existing issue or PR covers it, you create an issue.

Whether you fix it yourself and open a PR, or wait for someone else to do so — in either case, the PR is likely to sit unreviewed for months. And this isn't just my experience: it seems to be a widespread pattern across the repository.

I understand that the core team working on PrimeNG is small and always busy. Also, you don't want to bother a maintainer with pings. But the current situation is unsustainable and appears to be worsening over time. This leaves me with a few questions: What is the current process for community contributions? Are PRs still being reviewed, and if so, on what timeline? And how can the community best support the core team?

As a concrete example, here are PRs and discussions I opened without receiving any review:

• feat(select): Add tooltip support for options primeng#18432
• feat(multiselect): Add tooltip support for options primeng#18433
• feat(datepicker): Add support for using aria-describedby in datepicker primeng#18265
• fix(multiselect): add disabled binding to checkbox in disabled options primeng#18450
• fix(dialog): make dialog titles selectable primeng#19429
• fix(progressbar): use dynamic transition for fast value updates primeng#19419
• fix(datepicker): improve year selection logic in isYearSelected primeng#19417
• fix(datepicker): Enable dynamic updates for week numbers in datepicker primeng#18353
• https://github.com/orgs/primefaces/discussions/4062
• https://github.com/orgs/primefaces/discussions/4063

I'm raising this not to criticize, but because PrimeNG is a library many of us rely on and want to see succeed. I'm looking forward to an open conversation about this.