Two things I want to add that I swore were in the guide, but can't easily see them.
The first is triaging old JIRA issues. It is very valuable to be able to pick up old JIRA issues (opened against Solr 1.x, 2.x, 3.x, 4.x or even 5.x) and testing them against the latest release to see if the issue is still present or not. Often, they are no longer relevant, have been fixed or have not enough details to even figure out what the issue is. Adding a quick note to Jira for that, would help somebody else with the privileges to then resolve/close/mark-duplicate on the issue. And, you will learn a lot in the process of trying to figure out whether the issue is still present or not. I speak from personal experience here. If you do choose this path, let me know and I will share JIRA queries I used to quickly identify potential issues to review. Also, testing anything on Windows would be very helpful. Examples, Readme instructions, shipped extra libraries, etc. Most of the developers are not using Windows, so that's a bit of a dusty corner. And dusty corner with strange edge-case bugs around spaces, quotes, command line parameters and like. And yet again, doing this will give you cross-cutting understanding of Lucene/Solr, its various components and how they interact together. Regards, Alex. ---- http://www.solr-start.com/ - Resources for Solr users, new and experienced On 5 November 2017 at 04:43, Erick Erickson <[email protected]> wrote: > See: https://wiki.apache.org/solr/HowToContribute for both suggestions > on the kinds of things you could contribute (code isn't the only way!) > > After that, pick something specific that interests you. Are you a UI > wizard and would like to improve the admin UI? Want to grab a test > failure case and see if you can understand the root cause and fix it? > Tell us what you're interested in/skilled at and maybe we can give you > a first project. > > After that, you have to jump in and dig. If you want to start with the > code, check out the project (the link above will tell you how) and get > it compiling and set up in your IDE of choice, IntellIJ and Eclipse > are the most popular amongst the developers... > > And if you do want to work with the actual code, I'd dive into some > problem (see the JIRA list or failing tests) _and_ discuss the > approach you want to take after you've explored for a while. IOW, > don't think you need to have a solution before asking questions! > > Best, > Erick > > On Sat, Nov 4, 2017 at 7:01 AM, Shashank Tyagi <[email protected]> > wrote: >> +1 >> >> >> On Sat, Nov 4, 2017 at 4:08 PM, manish kakoti <[email protected]> >> wrote: >>> >>> Hello, >>> >>> I am new to Lucene, and i am really interested to contribute to it.How do >>> i actually get started with it? >>> Could use some suggestions and support in order to get started with it. >>> >>> Regards >>> Manish Kakoti >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
