Hi All, :wave: <@U58GRE73J> and I have been the p...
# ktlint
j
Hi All, 👋 @tapchicoma and I have been the primary maintainers of the ktlint-gradle plugin. Actually, honestly, @tapchicoma has been doing most of the work on the plugin for the past few years. Unfortunately, over the past few years, my personal ability to maintain the plugin has gone from actively writing to simply reviewing external contributions. @tapchicoma also has limited time of-late. However, I'm finding that I have limited time for even that these days. I'm not completely stepping away from the ktlint-gradle project, but what I am seeking is others to step in and help maintain the plugin. I'm looking for individuals who are interested in potentially taking on a larger role in the plugin's maintenance. I'd greatly appreciate assistance reviewing pull-requests and eventually passing along the tasks of cutting a release to others. I'm a security software engineer, so I understand the risks of just handing off a project to a stranger (eg. the event-stream), so I'm looking for someone to develop a rapport with. Please feel free to reach out if you're interested in getting involved with the project. Or simply start reviewing PRs or providing support on issues. Any support at this point would be greatly appreciated.
g
You should potentially x-post inside #opensource as well. You might find people interested to jump on over there.
j
Cool thanks
👍 1
r
I actually brought this up a few times, that we should probably make steps to integrate ktlint-gradle into the main ktlint repo, but @tapchicoma was against it as it would mean they are bound to the same release cycle 🙂 Anyway, I'd be happy to help, but please don't add me as a maintainer, so I don't feel pressured and committed, haha. I will try to look into issues and maybe fix some of them, and then see how it goes.
t
Now I am not against integrating it 🙂 But @Sha Sha Chu has doubts we will have capacity to support it as well
s
Haha if everyone agrees it makes the most sense we can bring it in. I just didn't want to commit us to more work if it seems that we're already overloaded