Question about project continuity and repository updates

[devpaulorcc]

I was even thinking about contributing a PR, but after seeing that this repository hasn't received updates since January 12, 2024, with several unanswered PRs, I was completely discouraged. I looked at the numbers and it seems that the project is somewhat abandoned.

Is this repository still alive or can I give up investing time in it? If there is still some development, it would be good to know, but with this history, I'm not very excited to keep trying.

I await a response.

[simenandre]

Thank you for sharing your concerns openly. While I understand your hesitation, I'd like to offer a different perspective:

Every thriving open-source project you see today has gone through periods of slower activity. What makes these projects successful isn't just consistent maintainer activity but passionate community members who step up when needed. Instead of viewing the current situation as discouraging, consider it an opportunity.

If you see unanswered PRs, you could:

1. Review them and provide feedback to help move them forward
2. Help test the changes
3. Update outdated PRs to resolve conflicts
4. Create documentation to make future contributions easier

Remember, open source is powered by people who see room for improvement and choose to be part of the solution. Your interest in contributing is precisely what keeps projects alive and growing.

If you have ideas for improvements, I would encourage you to share them. Even if response times are currently slow, your contribution could be the spark that helps reinvigorate the project. Would you be willing to share what changes you were thinking of implementing?

Note: I am not a maintainer or even contributor to this project currently.

[devpaulorcc]

It would be interesting if project maintainers or collaborators were more attentive to the continuous review of PRs, in order to keep the community active, guaranteeing growth and quality to the project. Considering the number of PRs without review or response, it is impossible not to notice that many developers end up unmotivated, as they are behind trying to contribute without any feedback.

It is essential that the community has the objective of truly adding value to the project, taking the lead and keeping the flame burning when there is no one to take on the responsibility of receiving and guiding contributions. However, this becomes difficult as only maintainers or contributors have the necessary permission to integrate other developers' changes into the official repository, limiting everyone's ability to contribute effectively.

This project, which is widely recommended as a valuable tool for professionals in my country, seems more like an illusion. The number of forks is a clear reflection of it being left out, which makes it seem like the repository was simply abandoned and is being dragged to be deprecated.

Maintainers and collaborators, I would like to know: has the project been abandoned or discontinued?

[braaar]

The project has not been abandoned. Yes, we've been in a bit of a lull since the lead maintainer experienced burnout, but even when this issue was created, the latest commit to develop was only a few months old.

For any further discussion, we can move to #1775

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.