Discussion: Future of this project and community maintenance 💭 #229
Description
OSCI holds a special place in my heart, and I know many of you feel the same considering how the project has grown from a very simple list through to what it has been more recently.
Since moving on from leading this project at EPAM, I’ve had numerous conversations with industry friends and open source leaders who continue to rely on this tool and see its immense value - it's become a little difficult to rely on it recently though for the reasons below. It’s clear that while the original focus from EPAM has shifted, the demand for these use cases has only grown and today more than ever it's important that we have a transparent and honest way of recognising and celebrating enterprise contributions to open source.
I’m posting this because I’m upset to see such a vibrant project lose its momentum and issues and pull requests go unanswered plus lots of great work that was done has been stripped and rolled back. I would love to start exploring a new path forward, whether that involves a fresh maintenance team, moving to a community-led model, or seeking a new home under a neutral foundation or another body.
This project still has a lot of "love" to give, and I’d hate to see this tool simply sunset itself for lack of a roadmap or maintainers which seems to be the case.
There's of course also some new thinking needed around how we handle the commit/email API changes mentioned here: #226
...finally, as an aside I have reached out to the project leads but have been hit with no responses so now's the time to get the community voice involved and decide what's next. Look forward to hearing your views.