I just tested this on my personal tiny Java project and it is (committer) +1 from me. Did not test it as part of a PR process, though would be super excited if I could retroactively graft it on my current one somehow: https://github.com/apache/lucene-solr/pull/1863
I've also signed up for the ApacheCon code bash and confirmed as mentor availability. How much time I will actually have is a question, but I will try. Hopefully, I will end up on a Solr team, there was no way to indicate that (Tom!). I would be super-curious to see how well it would be able to support Solr's gradle build with all the dark magic we seem to have in it. Regards, Alex. P.s. I suspect the full analysis of the code base would still be rather noisy, but since that's not a default flow of MuseDev, that should be fine. P.p.s. Medium term, I would love to write a custom check that complains about missing @since Javadoc tags for anything that is pluggable/module like, including Analyzers, UpdateRequestProcessors, Stream Components, etc. Knowing when each individual module is introduced is super useful for those on older versions and my previous attempts at fixing this required standalone code that even I cannot get to run again easily now. On Wed, 23 Sep 2020 at 11:56, Tom DuBuisson <to...@muse.dev> wrote: > > Lucene Developers, > > As part of our sponsorship of ApacheCon, our company MuseDev is doing a Bug > Bash for select Apache projects. We'll bring members of the ApacheCon > community together to find and fix a range of security and performance bugs > during the conference, and gameify the experience with teams, a leaderboard, > and prizes. The bash is open to everyone whether attending the conference or > not, and our whole dev team will also be participating to help fix as many > bugs as we can. > > We're seeding the bug list with results from Muse, our code analysis > platform, which runs as a Github App and comments on possible bugs as part of > the pull request workflow. Here's an example of what it looks like: > > https://github.com/curl/curl/pull/5971#discussion_r490252196 > > We explored a number of Apache projects and are reaching out because our > analysis through Muse found some interesting bugs that could be fixed during > the Bash. If this sounds familiar it's because I've been talking a bit on > this mailing list about Muse already. There has already been a bug fix based > on the tool findings, a prior conversation "Code Analysis during CI?", and a > PR adding configuration information for the GitHub App. > > We're writing to see if you'd be interested in having your project included > in the Bash. Everything is set up on our end, and while we're already working > with the infrastructure team to get lucene-solr added (with the PR and other > conversation as evidence of support) it would help if you say yes on this > listserv as a clear signal to the Apache Infrastructure team to grant Muse > access to your Github mirror. > > We'll then make sure it's all set-up and ready for the Bash. And of course, > everyone on the project is most welcome to join the Bash and help us smash > some bugs. > > -Tom --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
