The short form is "join the community". Shawn did so as he explained.
A _great_ place to contribute is to write unit tests. That's also a bit "safe" in that it doesn't change Solr but does improve it! Poke around the build site and look at the coverage reports, pick a part of Solr that isn't tested and create some. Improve the documentation. Join the effort to revamp the website. Pick the part of Solr that was least clear to you and improve it. And on and on.... And I flat guarantee that if you could get to the bottom of the distributed test failures that seem to occur fairly regularly, you'd have the undying gratitude of multiple committers :).. Warning though, that code is fairly hairy! Best, Erick On Fri, May 16, 2014 at 10:05 PM, Shawn Heisey <s...@elyograg.org> wrote: > On 5/15/2014 6:10 AM, Mukundaraman valakumaresan wrote: >> How to become a solr committer? Any suggestions? > > For me, this question has personal relevance. > > In 2010, I began to integrate Solr into our environment. I joined the > mailing list, asked questions, stumbled around quite a lot. Eventually > I got my install working very well, and I discovered that when others > would ask questions, I sometimes knew the answer, so I started answering > a lot more questions than I asked. > > Eventually, I also joined the dev list, began to learn Java, and started > contributing patches, mostly to issues that I would file myself, but > sometimes for other issues. My name ended up in the CHANGES.txt more > than once. A little over a year ago, the Lucene PMC asked me to become > a committer. I was not pursuing this as a goal, so it was completely > unexpected. I accepted the offer. > > My advice would be to put some serious time and effort into making Solr > better. As the following wiki page says, this involves a lot more than > writing code. > > http://wiki.apache.org/solr/HowToContribute > > Thanks, > Shawn >
