[FFmpeg-devel] [RFC] beginner difficulty bug trac tag for new open source developers

Sami Hult sami.hult at gmail.com
Mon Jul 4 12:43:03 EEST 2016


On 4 July 2016 at 11:02, Clément Bœsch <u at pkh.me> wrote:

> 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.
>

I think Randall has it right about bugs :)

http://xkcd.com/1700/

OTOH as someone new to ffmpeg ecosystem I think one could benefit from more
clear documentation on contribution.

I'm myself working on several projects - not all of them are
computer-related - and trying to contribute features or changes that I find
useful for myself is a spare moment thing. One of the surprises along the
way was "won't compile". Sure it did, just not with hardening features
enabled (which I think ARE useful).

My five cents would be to advice every aspiring contributor to focus on
bugs or lacking features that are an issue for themselves. That ensures
motivation to really fix it :)


More information about the ffmpeg-devel mailing list