Proposal for Expanding Maintenance Team

[ThomasSanson]

trafficstars

Dear @di-sukharev,

I hope this message finds you well. Firstly, I would like to extend my sincere appreciation for your work on the opencommit repository. It's a fantastic project that has garnered a lot of interest and contributions from the community.

I have noticed that there is a significant number of pull requests awaiting review, which is a testament to the project's popularity and the community's eagerness to contribute. However, it also appears that the current maintenance bandwidth is somewhat limited, which is completely understandable given the demands of managing such a project.

To help address this and ensure the continued growth and health of the opencommit project, I would like to propose the idea of expanding the maintenance team. This would allow for more efficient management of contributions and could help in further enhancing the project's capabilities and reach.

Adding more maintainers could offer several benefits:

1. Faster response times for pull requests and issues.
2. Diverse perspectives and expertise to improve the quality and functionality of the project.
3. Reduced workload for you, allowing more focus on strategic direction and innovation.

I understand that selecting maintainers is a significant decision, and it's essential to ensure that they are trustworthy and aligned with the project's goals. If you are open to this idea, I am more than willing to assist in any way I can, be it in the selection process or even as a potential maintainer, should you deem it appropriate.

Thank you for considering this proposal. Your dedication to the opencommit project is greatly appreciated, and I am excited about the potential of what we can achieve together with a slightly expanded team.

Best regards

[github-actions[bot]]

Stale issue message

[di-sukharev]

haha, thank you @ThomasSanson, im here!

i will be now reviewing issues and merging PRs each weekend, lets build! btw, im thinking about doing local code review before committing the message, wdyt?

❤️ @benjefferies @DuNuNuBatman, @garrettg123, @senovr, @camel2243, @jacob1379, @spinute ❤️

[di-sukharev]

i think i should also mention @malpou, @jaroslaw-weber, @sebastienfi, @avighnac, @jlopezlira, @zavodnyuk, @evandeininger, @joshuahamlet, @matt-degraffenreid, @nader-zouaoui and all who contributed to OpenCommit

thank you guys ❤️

[sebastienfi]

I volunteer to join the maintenance team, that's a great initiative. I have a few ideas to improve arch and features, and I have a couple hours every two days to review, test, and merge.

[di-sukharev]

@sebastienfi thank you! i've reopened all the "marked as stale issues" and PRs, it's a lot, could you please take a look at them too, please share your thoughts, tag me if needed, let's start by looking together at what is hanging, close/address the issues and build the bigger picture of priorities, wdyt?

[spinute]

That’s great to hear from @di-sukharev!

I tried several utilities like opencommit these days, and I found opencommit to be the best one for my use case.

I'm really interested in configurable prompts/behaviors and better handling of large diffs. I found PRs/issues about these features, so it seems some people also want them.

I can use my time to implement/review/support these features as well.

[di-sukharev]

@spinute thank you! <3

For the large diffs, i originally wanted to split it in this function splitDiff(diff: string, maxChangeLength: number), it didnt work well, but it worked, then larger context models were introduced and i thought they can handle large diffs better, but anyway introduce any of your ideas about anything, i'm happy to help you

wdyt about finding those hanging issues/prs which interest you the most, tag me and we go from there?

[sebastienfi]

Seems a good idea to tag issues, close these which really are stale. Then we could pick which to prioritize, and get done with it.

To begin with tags:

• bug
• improvement / feature / suggestion
• documentation

[di-sukharev]

Let's start with tagging the issues opened and go from there. I also have "local code review" in mind, but lets first see the bigger picture and what people want us to build in the issues

[di-sukharev]

i reopened all stale issues, there might be some that we can close, i will be reviewing it on Saturday, feel free to join by starting with any opened issue

[di-sukharev]

merged and tested 2 PRs, released 3.0.10, got no more time to go over issues to help people there and tag @sebastienfi @spinute if you find few minutes—please help with the issues <3

[sebastienfi]

@di-sukharev LGTM I'll work on it today. Would be nice to give true capabilities to maintenance team:

• add labels to issues
• close issues, mark as stale
• approve and eventually, merge, PRs. Example here

This way we can scale and not wait for your approval for every task.

[di-sukharev]

@sebastienfi will do on the coming weekend, thank you guys <3 <3 <3

[di-sukharev]

@sebastienfi didnt have time today, will have 10x more time from tuesday ;)

[di-sukharev]

still busy, but anyway getting to it tmr

[di-sukharev]

@sebastienfi cant find a quick option where you can do everything, but not too much... for now please mention me in every PR you want to merge like we did here, gonna merge it quickly

[di-sukharev]

3.0.12 is out, please npm i -g opencommit