It would be great if the first project is provided from solr/lucene's end,
because it will help me get a direction and move further and later on
contribute to the code effectively

On Sun, Nov 5, 2017 at 12:27 AM, manish kakoti <[email protected]>
wrote:

> Although i have not explored the complete codebase yet, but i want to dive
> into the code and work with it
>
> On Sat, Nov 4, 2017 at 11:13 PM, 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]
>>
>>
>

Reply via email to