On 7/7/20, Nicolas George <geo...@nsup.org> wrote: > Jean-Baptiste Kempf (12020-07-05): >> With tools and organization. > > Sure, but you are forgetting one wing: responsibility. > > The reason many patches go a long time without review is that nobody > feels responsible for reviewing them. > > If it is an area of the code we know well, an area for which we have > maintainership, or if it seems to be tangent to a pet-peeve of ours, we > will have a look at it. > > But otherwise, we will have a more-or-less cursory look at it, and > assume somebody else will worry about it. > > It could be decided that authority in this project comes with the duty > of doing some amount of boring review. (And doing it properly: if > Coverity goes fireworks each time somebody approves a patch, they're not > reviewing properly.) > > Probably another discussion to have once we have the structures to > decide. >
Yes, I still remember EOF saga in libavformat and unwillingness to fix all regressions in timely manner, that caused similar issues also in external projects. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
