2017-02-25 15:59 GMT+01:00 wm4 <nfx...@googlemail.com>: > I'm documenting existing practice.
> -@subheading Always wait long enough before pushing changes > +@subheading Always wait long enough before pushing changes to code actively > maintained by others I suspect this is missing an exception for security issues if you want to document the actual practice. > +@subheading Pushing patches without sending them to the mailing list > +If you're the maintainer of a file, or the file is not actively maintained by > +anyone, or the file is not covered by the MAINTAINERS file, you can just push > +them without asking for permission, and without sending them to ffmpeg-devel. > +This right only applies to developers with git push access, of course. > +A maintainer is considered not active if he hasn't posted a mail to > ffmpeg-devel > +for longer than 6 months, and hasn't pushed a patch in that time period > himself. Unfortunately, there are maintainers who are happy to review patches sent to improve their code but the files were not touched for more than six months so they did not seem active for more than six months. Carl Eugen _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
