Hey Neha, I like all these ideas.
I think people have been doing a good job with the newbie label, which is great, we should keep doing that. I think pairing people up is a great idea. The trick is actually figuring out who has an interest in becoming a committer and would like a pair, and who is just dropping a one-off-patch. I like the idea of having someone assign JIRAs with patches to committers for review. So the proposed workflow would be: 1. Have a designated triage person go through all JIRAs. If a JIRA comes in with a patch or the person says they are working on something, the triage person will assign the JIRA to a random committer to handle review. If the committer is too busy they can hand it off to another random contributor until it lands on someone who can do it. It would be nice if the committer could get to it in < 2 days (even if they are just punting it to someone else) so that people don't have to wait too long. 2. The assigned committer then reviews the patch. If it needs more work they assign it back to the contributor. If it is good as is they commit it and close the JIRA. If no objections, let's use this approach for managing patches. I think it is kind of what we have been doing informally, but this will make it clear. -Jay On Thu, Jul 17, 2014 at 7:00 AM, Neha Narkhede <neha.narkh...@gmail.com> wrote: > Thanks Jay for bringing this up. A couple things might help - > > 1. Be diligent in marking newbie/newbie++ labels. I've seen us do pretty > well here. > 2. Pair up contributors to committers for a few initial patches to ensure a > smoother ramp up. I've recently done this and have seen it work pretty > well. Happy to help more. > 3. Jay and I talked about ways of improving patch review turnaround time. > Mostly, the problem is that committers are either swamped or not sure which > patches need review. What might work is to assign the JIRA to a committer > for review and have the committer shepherd the patch to checkin and > reassign the JIRA back to the contributor. I can help with triaging and > assigning committers to patch reviews and over time most of the committers > will be able to do this. > > Thanks, > Neha > > > On Wed, Jul 16, 2014 at 10:26 PM, pushkar priyadarshi < > priyadarshi.push...@gmail.com> wrote: > >> I have been using kafka for quite some time now and would really be >> interested to contribute to this awesome code base. >> >> Regards, >> Pushkar >> >> >> On Thu, Jul 17, 2014 at 7:17 AM, Joe Stein <joe.st...@stealth.ly> wrote: >> >> > ./gradlew scaladoc >> > >> > Builds the scala doc, perhaps we can start to publish this again with the >> > next release and link it on the website. For more related check out the >> > README >> > >> > >> > /******************************************* >> > Joe Stein >> > Founder, Principal Consultant >> > Big Data Open Source Security LLC >> > http://www.stealth.ly >> > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> >> > ********************************************/ >> > >> > >> > On Wed, Jul 16, 2014 at 8:39 PM, hsy...@gmail.com <hsy...@gmail.com> >> > wrote: >> > >> > > Is there a scala API doc for the entire kafka library? >> > > >> > > >> > > On Wed, Jul 16, 2014 at 5:34 PM, hsy...@gmail.com <hsy...@gmail.com> >> > > wrote: >> > > >> > > > Hi Jay, >> > > > >> > > > I would like to take a look at the code base and maybe start working >> on >> > > > some jiras. >> > > > >> > > > Best, >> > > > Siyuan >> > > > >> > > > >> > > > On Wed, Jul 16, 2014 at 3:09 PM, Jay Kreps <jay.kr...@gmail.com> >> > wrote: >> > > > >> > > >> Hey All, >> > > >> >> > > >> A number of people have been submitting really nice patches >> recently. >> > > >> >> > > >> If you are interested in contributing and are looking for something >> to >> > > >> work on, or if you are contributing and are interested in ramping up >> > > >> to be a committer on the project, please let us know--we are happy >> to >> > > >> help you help us :-). It is often hard to know what JIRAs or >> projects >> > > >> would be good to work on, how hard those will be, and where to get >> > > >> started. Feel free to reach out to me, Neha, Jun, or any of the >> other >> > > >> committers for help with this. >> > > >> >> > > >> Cheers, >> > > >> >> > > >> -Jay >> > > >> >> > > > >> > > > >> > > >> > >>
