Repository navigation
Proposal: Expanding the project maintenance team #300
Description
Hi @jnothman,
Thank you for all the work you've done on upsetplot! This project is very useful and widely appreciated by the community.
I've noticed that there are currently several open issues and PRs, and I was wondering if it might be worth expanding the maintenance team a bit to give you a hand. Several contributors seem motivated to help evolve the project.
The original goal of this package was to replace py-upset, which was no longer maintained. It would be unfortunate if the same thing happened to upsetplot.
Here are some possible options:
Option 1: Direct access
You could grant "Triage" or "Write" access to a few regular contributors. This would allow them to:
- Triage and label issues
- Review and merge PRs
- Maintain the project more actively
Option 2: Create an organization
Transfer the project to a dedicated GitHub organization. This has the advantage of:
- Ensuring the project's longevity beyond individual contributions
- Making it easier to pass on responsibilities if needed
- Building a real maintenance team
Of course, you would keep a central role and control over the project's direction. The idea is simply to support you and make the project more dynamic.
What do you think? I'd be happy to discuss this in more detail if you're interested.
Thanks again for your work!
Activity
ericmjl commentedon Apr 7, 2026
I'd like to upvote on this, and would love to chip in to help!
Dorah3D commentedon Jun 1, 2026
Unfortunately, it seems that this repo is no longer mantained by the author. However, i recently discovered a very nice library that also deals with Upset plots called Marsilea. Maybe there might be some room for help in that repo.