Re: [Discuss] patch review virtual hackathon

2018-04-05 Thread kurt greaves
To add to the above, hackathons would make sense in the lead up to the feature freeze IMO to get things through the door, but not necessarily afterwards (debatable). And they can be flexible too; I suspect once people start on reviewing something they'll be much more likely to see it through to

Re: [Discuss] patch review virtual hackathon

2018-04-05 Thread kurt greaves
I like the idea and we would be willing to take part (no committers here but I'm sure we can help). I think it better to pick some JIRAs per 2-3 weeks and have people review > them. In my experience, it is hard to synchronize all people across > companies during one 72 hour slot. It is hard,

Re: [Discuss] patch review virtual hackathon

2018-04-05 Thread Nate McCall
That could work as well. My goal is that we figure out how to resource and focus on this for a bit. On Fri, Apr 6, 2018, 5:02 PM sankalp kohli wrote: > I think it better to pick some JIRAs per 2-3 weeks and have people review > them. In my experience, it is hard to

Re: [Discuss] patch review virtual hackathon

2018-04-05 Thread sankalp kohli
I think it better to pick some JIRAs per 2-3 weeks and have people review them. In my experience, it is hard to synchronize all people across companies during one 72 hour slot. On Thu, Apr 5, 2018 at 9:48 PM, Nate McCall wrote: > Per Kurt's point in our release thread, we