[FFmpeg-cvslog] doc/developer.texi: extend the argument for submitting patches

[Anton Khirnov]

ffmpeg | branch: master | Anton Khirnov <anton at khirnov.net> | Wed Nov  9 14:59:21 2022 +0100| [c0c492dd47c76c4ef45ddc565f34b451981b2088] | committer: Anton Khirnov

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

Stop talking about commercial programs, since this applies to any
downstream user.

> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=c0c492dd47c76c4ef45ddc565f34b451981b2088
---

 doc/developer.texi | 20 +++++++++++++++-----
 1 file changed, 15 insertions(+), 5 deletions(-)

diff --git a/doc/developer.texi b/doc/developer.texi
index 5cf3b19ee0..2f0d2b7daa 100644
--- a/doc/developer.texi
+++ b/doc/developer.texi
@@ -24,11 +24,21 @@ generated from the headers
 the examples under @file{doc/examples}
 @end itemize
 
-You can use the FFmpeg libraries in your commercial program, but you
-are encouraged to @emph{publish any patch you make}. In this case the
-best way to proceed is to send your patches to the ffmpeg-devel
-mailing list following the guidelines illustrated in the remainder of
-this document.
+If you modify FFmpeg code for your own use case, you are highly encouraged to
+ at emph{submit your changes back to us}, using this document as a guide. There are
+both pragmatic and ideological reasons to do so:
+ at itemize @bullet
+ at 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.
+ at item
+FFmpeg developers include leading experts in the field who can find bugs or
+design flaws in your code.
+ at item
+By supporting the project you find useful you ensure it continues to be
+maintained and developed.
+ at end itemize
 
 For more detailed legal information about the use of FFmpeg in
 external programs read the @file{LICENSE} file in the source tree and