Re: [Discuss] patch review virtual hackathon
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 completion. It's unlikely we'd end up with many commits after 72 hours, purely because any feedback may take longer than that to be actioned, but that doesn't mean our time is wasted. On 6 April 2018 at 05:09, kurt greaveswrote: > 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, but there are benefits. Mostly having many people all actively > reviewing stuff at the "same" time so communication will be much > easier/more natural. I think a plan like ^ should be done as well as a > hackathon, but should be a continuous thing that we always do. E.g, each > week someone is responsible for picking a few tickets that should be > reviewed and we hunt for volunteers to start the review work. > > >> > > >> >> On Thu, Apr 5, 2018 at 9:48 PM, Nate McCall wrote: >> >> > Per Kurt's point in our release thread, we have a lot to do here. >> > >> > What do folks feel about setting aside a 72hr period at some point soon >> > where we get some allotment from our employers to spend a window or two >> of >> > time therein reviewing patches? >> > >> > I have seen a couple of other ASF communities do this type of thing >> > effectively in recent months. If we pull this off I think it could set >> an >> > excellent precedent for swarming on other things in the future. >> > >> > >
Re: [Discuss] patch review virtual hackathon
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, but there are benefits. Mostly having many people all actively reviewing stuff at the "same" time so communication will be much easier/more natural. I think a plan like ^ should be done as well as a hackathon, but should be a continuous thing that we always do. E.g, each week someone is responsible for picking a few tickets that should be reviewed and we hunt for volunteers to start the review work. > > > On Thu, Apr 5, 2018 at 9:48 PM, Nate McCallwrote: > > > Per Kurt's point in our release thread, we have a lot to do here. > > > > What do folks feel about setting aside a 72hr period at some point soon > > where we get some allotment from our employers to spend a window or two > of > > time therein reviewing patches? > > > > I have seen a couple of other ASF communities do this type of thing > > effectively in recent months. If we pull this off I think it could set an > > excellent precedent for swarming on other things in the future. > > >
Re: [Discuss] patch review virtual hackathon
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 kohliwrote: > 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 have a lot to do here. > > > > What do folks feel about setting aside a 72hr period at some point soon > > where we get some allotment from our employers to spend a window or two > of > > time therein reviewing patches? > > > > I have seen a couple of other ASF communities do this type of thing > > effectively in recent months. If we pull this off I think it could set an > > excellent precedent for swarming on other things in the future. > > >
Re: [Discuss] patch review virtual hackathon
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 McCallwrote: > Per Kurt's point in our release thread, we have a lot to do here. > > What do folks feel about setting aside a 72hr period at some point soon > where we get some allotment from our employers to spend a window or two of > time therein reviewing patches? > > I have seen a couple of other ASF communities do this type of thing > effectively in recent months. If we pull this off I think it could set an > excellent precedent for swarming on other things in the future. >
[Discuss] patch review virtual hackathon
Per Kurt's point in our release thread, we have a lot to do here. What do folks feel about setting aside a 72hr period at some point soon where we get some allotment from our employers to spend a window or two of time therein reviewing patches? I have seen a couple of other ASF communities do this type of thing effectively in recent months. If we pull this off I think it could set an excellent precedent for swarming on other things in the future.