[GH-ISSUE #1124] Project Maintenance #815

Open
opened 2026-03-04 01:07:56 +03:00 by kerem · 0 comments
Owner

Originally created by @ossenthusiast on GitHub (Sep 27, 2025).
Original GitHub issue: https://github.com/rivo/tview/issues/1124

Hi @rivo,

First of all, thank you for all the work you’ve put into tview—it’s clearly a project that a lot of people enjoy to work with and depend on.

I’ve noticed that there are quite a few open issues and PRs, including feature requests that haven’t received much feedback or movement. That’s completely understandable since maintaining a project of this size and popularity can be a lot for one person to handle. (https://github.com/rivo/tview/issues/743)

Would you be open to bringing on additional maintainers or collaborators who could help with:

  • Reviewing and triaging PRs (merging or closing as needed)
  • Giving feedback on feature requests and potential workarounds
  • Helping keep the issue tracker organized

This could lighten your load and help keep contributions flowing while still keeping you in control of the project’s overall direction. If you’d prefer to keep it smaller in scope, even adding someone just to help with triage could already make a big difference.

What do you think? Would you be open to discussing this? Thanks again for your time and for maintaining such a great library!

Originally created by @ossenthusiast on GitHub (Sep 27, 2025). Original GitHub issue: https://github.com/rivo/tview/issues/1124 Hi @rivo, First of all, thank you for all the work you’ve put into tview—it’s clearly a project that a lot of people enjoy to work with and depend on. I’ve noticed that there are quite a few open issues and PRs, including feature requests that haven’t received much feedback or movement. That’s completely understandable since maintaining a project of this size and popularity can be a lot for one person to handle. (https://github.com/rivo/tview/issues/743) Would you be open to bringing on additional maintainers or collaborators who could help with: * Reviewing and triaging PRs (merging or closing as needed) * Giving feedback on feature requests and potential workarounds * Helping keep the issue tracker organized This could lighten your load and help keep contributions flowing while still keeping you in control of the project’s overall direction. If you’d prefer to keep it smaller in scope, even adding someone just to help with triage could already make a big difference. What do you think? Would you be open to discussing this? Thanks again for your time and for maintaining such a great library!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/tview#815
No description provided.