On Sun, Jul 03, 2016 at 02:29:31PM -0400, compn wrote: [...] > i'm also not suggesting tagging every bug with a difficulty rating , as > that would take a while and i'm not sure of the benefit. i just want to > have a solid number (100-300+) of bugs that are somewhat easy to > understand, implement, review and finish.
I'd say there is probably no easy bug opened, or very few (a hand at best). Most of the easy bugs are solved as soon as they show up, because they are generally related to a recent feature on which the author is still available and working on. The other easy bugs are stuff like typo/spelling etc. You could re-read all the documentation and look for inconsistencies for instance. It's not hard, but it's just boring as shit. Now if you let the user rate the difficulty, they're going to say "hey it's easy, fix it quick for me", but they have no clue whatsoever. As a result, I'm not convinced that's a good idea. -- Clément B.
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
