Niranjan I would suggest few personal opinions - - Pick up minor and trivial jira's which are easy to start. You dont want to spend a lot of time stuck with ur first jira.
- You can pick up jira filtered by component of your interest instead of a random jira. Timothy's blog and Drill wiki will tell you lot about different components of drill. - Ask questions about stuffs when you feel lost - someone would definitely help you out. - Join our Drill hangout on 1st tuesday of every month. We sometimes have it bi-monthly. Its a great way to know team and different active areas with ongoing work. Ofcourse these are my personal opinions which i found helpful. Good luck Drilling. On 09/01/2015 12:49 pm, "Maisnam Ns" <[email protected]> wrote: > > Yash , Timothy and Ted, > > Thanks all for your suggestions. > > Yash, > As I am new to Drill I would like to go first with some bug fixes first as > I need to learn how Drill works and honestly speaking , right now I have > just started learning Drill. When I have done enough bug fixing I would > like to come up with new features, but for the moment I would be looking > for bugs which are easy to be fixed something like taking baby steps on > Drill. > > > Hope to see you all soon . > > Regards > Niranjan > > > > On Fri, Jan 9, 2015 at 11:26 AM, Ted Dunning <[email protected]> wrote: > > > On Thu, Jan 8, 2015 at 8:43 PM, Maisnam Ns <[email protected]> wrote: > > > > > 1. Is it fine with other Drill contributors that if I find an unassigned > > > bug , can I assign it to myself and start working on it or do I need to > > > send a specific mail to any specific person if so to whom ? > > > > > > > Don't worry about assigning the bug. Just start commenting on it about the > > approach that you would like to take. > > > > > > > 2. I found a how to contribute to Drill section on one of the links that > > I > > > have seen but is there a Developer documentation so that I can speed up > > my > > > understanding of the codebase. > > > > > > > Parts of the code base are a bit intense and can be hard to work through. > > One helpful thing you can do is ask questions about difficult parts and > > when you get good answers, suggest patches to the web-site or to the code > > that make those sections easier to understand. This helps you and helps > > the project in a way that only a newcome can really do ... that is, to see > > the project and the code with new eyes. > >
