Hi all. Yeah, it's me again. There are a lot of patches in gerrit that aren't making much progress, because they're waiting for reviews.
100% I get it: maintainer time is very valuable. (I was just reading someone's paper on how maintainers should not be giving away their time for free on random code reviews, because they have so little of it. I don't agree with everything in the paper, but the problem is definitely there). The project already has in place a LOT of stuff which helps - automated builds, automated unit testing, other automated tool runs which help a vote... the maintainer or other code reviewer can know the patch will apply and will build etc. It's also really hard on people trying to improve things if it takes so long to get their changes through that they either have to spend more time rebasing multiple times, or they just give up and stop maintaining their patch. Is there any way we can do better? _______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
