oss-apps
Meta: Consider Adding Collaborators or Maintainers?
Hi @KMKoushik
First of all, thank you for this fantastic project! It’s a great piece of software that I keep pushing on my friends, and it’s clear that a lot of thought and effort has gone into it. 🙏
Over the last few months, the project has seen some really valuable contributions from the community — several PRs and issues have been opened that could significantly enhance the functionality and usability of the software. However, with limited maintainer activity recently, some of these improvements are currently in limbo.
I completely understand that this is a hobby project and you therefore only have limited time to spend on it/have other priorities. To help sustain the momentum and continue evolving the project, would it then maybe make sense to consider adding one or more trusted community contributors as maintainers or collaborators? Even limited access - for reviewing and merging PRs or triaging issues - could go a long way.
In any case, just opening this discussion in the hope of finding a way to keep the community engaged and the project moving forward.
Thanks again for your work 🙌
Totally support the idea in Issue #213. Split Pro has a great community, but progress is slow with only one maintainer. Adding a few trusted collaborators would speed up reviews, keep things moving, and make it easier for contributors to stay engaged. Would love to see the project grow with more hands on deck!
Yeah totally agree, I mean someone could fork it, and then that one could become the "new" maintained version, but I would be better if it was kept in the original repo!
I guess @KMKoushik is probably pretty busy with his unsend project so this would be really nice.
hello guys, yes as you guessed, it's very hard for me to work on this with a 4m old baby, full time job and trying to make money from a open source project.
if you guys are interested to be co-maintainers, i'm down for it. we can go for quick call and i'll add few trusted people
Hey, no justification needed! you could even just be bored of it and that would be fine 😀 it's always better to maintain as a community than a sole person :)
@KMKoushik Hey, no problem at all. Totally understandable! And yeah, I’d like to be one of the maintainers 😊
I guess I should have written this sooner ;) I have been given merge and release permissions to keep the project going and hope to run this project in a release cycle of:
- 1-2 "big" features/changes per minor release
- smaller tasks and fixes to locate regressions
With features I want to first focus on polishing out the core functionalities one would expect from an Expense app or Splitwise alternative and later move on to adding more shiny or niche features. I know that using BigInts in DB or refactoring balances might not sound too exciting, but the codebase looked like it was vibe coded and there are many paper cuts that need to be taken care of first.
Anyways, I also want the shiny features, but we are not there yet. The pace with 1.5 was low due to the holiday season, but I'm back now and if any of you would like to help out or get more organized as a community, don't hesitate to submit PRs, open discussions and reach out!