virtualenv/FFmpeg
1
0
Fork 0
mirror of https://github.com/FFmpeg/FFmpeg.git synced 2025-01-24 13:56:33 +02:00
Code Issues Releases Activity

doc/developer.texi: extend the argument for submitting patches

Browse Source 
Stop talking about commercial programs, since this applies to any
downstream user.
This commit is contained in:
Anton Khirnov 2022-11-09 14:59:21 +01:00
parent 26080d1542
commit c0c492dd47
1 changed files with 15 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/developer.texi
View File

@ -24,11 +24,21 @@ generated from the headers
the examples under @file{doc/examples} the examples under @file{doc/examples}
@end itemize @end itemize
You can use the FFmpeg libraries in your commercial program, but you If you modify FFmpeg code for your own use case, you are highly encouraged to
are encouraged to @emph{publish any patch you make}. In this case the @emph{submit your changes back to us}, using this document as a guide. There are
best way to proceed is to send your patches to the ffmpeg-devel both pragmatic and ideological reasons to do so:
mailing list following the guidelines illustrated in the remainder of @itemize @bullet
this document. @item
Maintaining external changes to keep up with upstream development is
time-consuming and error-prone. With your code in the main tree, it will be
maintained by FFmpeg developers.
@item
FFmpeg developers include leading experts in the field who can find bugs or
design flaws in your code.
@item
By supporting the project you find useful you ensure it continues to be
maintained and developed.
@end itemize
For more detailed legal information about the use of FFmpeg in For more detailed legal information about the use of FFmpeg in
external programs read the @file{LICENSE} file in the source tree and external programs read the @file{LICENSE} file in the source tree and