Need a maintainer?

[jonkoops]

Hi, I noticed that there are quite a few PRs and issues out there, and that the last commit and release was made in 2022. If you need to have an additional maintainer feel free to send me an invite, or otherwise close this issue.

[ruvasik]

You can fork it ;-)

[jonkoops]

You can fork it ;-)

That is not an option. It would never have the user-base this package already has, leaving all those existing users without any of the benefits.

[SaptatirthaChoudhury]

Can you tell me how to understand this codebase that I can contribute?

[jonkoops]

Can you tell me how to understand this codebase that I can contribute?

If you want to contribute I suggest you first familiarize yourself with the code-base and related technologies first, to ensure your contribution is of good quality. Then try to solve issues that have already been identified in the backlog and can be solved, rather than creating new PRs that might fix things that apply only to you and might be problematic to triage.

This project clearly doesn't currently have the capacity currently to take on more contributions without first having a maintainer to steward such contributions, so I would not waste your time and potentially get demotivated whilst your work stalls.

There are plenty of active open-source projects in need of contributions, I would recommend looking elsewhere for now, at least until someone takes over this project.

[SaptatirthaChoudhury]

Ok atleast tell me what are the technologies and best practices I have to do for my knowledge. My intention is to increase my skills through this overwhelming codebase that's it.

…

On Sun, Mar 24, 2024, 23:34 Jon Koops ***@***.***> wrote: Can you tell me how to understand this codebase that I can contribute? If you want to contribute I suggest you first familiarize yourself with the code-base and related technologies first, to ensure your contribution is of good quality. Then try to solve issues that have already been identified in the backlog and can be solved, rather than creating new PRs that might fix things that apply only to you and might be problematic to triage. This project clearly doesn't currently have the capacity currently to take on more contributions without first having a maintainer to steward such contributions, so I would not waste your time and potentially get demotivated whilst your work stalls. There are plenty of active open-source projects in need of contributions, I would recommend looking elsewhere for now, at least until someone takes over this project. — Reply to this email directly, view it on GitHub <#870 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJUCTC25RKQXCMC5ZGGA47DYZ4IRZAVCNFSM6AAAAAA6UYVGPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJWHA4DQNBZGY> . You are receiving this because you commented.Message ID: ***@***.***>

[jonkoops]

Sorry, don't have the time for that. And I can pretty much tell you nobody here will have the time to do so. I'd recommend you start on an actively maintained project that has issues marked as 'help wanted' or 'good first issue'.

[SaptatirthaChoudhury]

No problem, I understand. Thanks

…

On Thu, Mar 28, 2024 at 3:50 PM Jon Koops ***@***.***> wrote: Sorry, don't have the time for that. And I can pretty much tell you nobody here will have the time to do so. I'd recommend you start on an actively maintained project that has issues marked as 'help wanted' or 'good first issue'. — Reply to this email directly, view it on GitHub <#870 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJUCTC4G364GGR6BM23KIATY2POFRAVCNFSM6AAAAAA6UYVGPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRUHA2TANJXGU> . You are receiving this because you commented.Message ID: ***@***.***>

[jarble]

@ruvasik If you are no longer maintaining this repository, you can transfer it to another user.

[jonkoops]

Also calling @thornjad, let me know if I can help out.