[FFmpeg-devel] [PATCH] add CONTRIBUTING.md
gajjanag at mit.edu
Tue Oct 6 03:46:42 CEST 2015
On Mon, Oct 5, 2015 at 7:26 PM, Lou Logan <lou at lrcd.com> wrote:
> For the Github users to ignore.
> Signed-off-by: Lou Logan <lou at lrcd.com>
> CONTRIBUTING.md | 36 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 36 insertions(+)
> create mode 100644 CONTRIBUTING.md
> diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
> new file mode 100644
> index 0000000..4bccf25
> --- /dev/null
> +++ b/CONTRIBUTING.md
> @@ -0,0 +1,36 @@
> +# Contributing to FFmpeg
> +FFmpeg is a big project, but we like seeing patches from new contributors.
> +You can get started by reading the [Developer Documentation]
> +## A note to Github users
> +**FFmpeg development, including patch reviews, occurs on the ffmpeg-devel
> +mailing list, so most developers do not view Github pull requests.
> +Therefore, Github pull requests should be avoided because they will
> +likely be not be noticed.**
Unless you have a good reason for this, please change the paragraph to
be much more similar/identical with README.md.
> +## Submitting patches
> +Patches should be sent to the [ffmpeg-devel mailing list]
> +Patches created with `git send-email` are preferred, but using
> +`git format-patch` is also acceptable. See [Submitting Patches]
> +(http://ffmpeg.org/developer.html#Submitting-patches-1) and
> +[Using Git to Develop FFmpeg](https://ffmpeg.org/git-howto.html).
> +## Bug reports
> +Bug reports and feature requests should be submitted to our
> +[bug tracker](https://trac.ffmpeg.org/). For more information refer to
> +[Submitting a Bug Report](https://ffmpeg.org/bugreports.html).
> +Please do not send bug reports to the ffmpeg-devel mailing list unless
> +you are also sending a patch to fix the bug.
> +## If you need help
> +Visit the #ffmpeg IRC channel, or send a message to one of the
> +appropriate [mailing lists](https://ffmpeg.org/contact.html).
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
More information about the ffmpeg-devel