Romain Beauxis (HE12025-08-01): > Part of my question is: how should people know what are the area you > are responsible for and who to contact when working on specific areas?
I know it and I am perfectly fine with reading the summary line of every submitted patch to see if I need to open it. Anything less would be irresponsible for somebody who have contributed to multiple parts of the code anyway. The issue is afterwards. Right now, if the summary tells me I should be interested, it takes me one key to start reading the patch and one key to start reviewing it. With the new proposal, it takes multiple clicks: that is not acceptable. Our problem is not that we do not get enough patches, our problem is that we do not have enough people with the knowledge and will to review them. So, how would you qualify a measure that (1) brings more patches and (2) cause more work to the people who might review them? Regards, -- Nicolas George _______________________________________________ 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".
