From: michaelni <code@ffmpeg.org> To: ffmpeg-devel@ffmpeg.org Subject: [FFmpeg-devel] [PATCH] doc/developer: Basic documentation for Source Plugins (PR #20197) Date: Sat, 9 Aug 2025 17:22:32 +0300 (EEST) Message-ID: <20250809142232.473C668D0FE@ffbox0-bg.ffmpeg.org> (raw) PR #20197 opened by michaelni URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20197 Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20197.patch Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> From 23b2e9eac15db42517c977bcaa7fa9446cb54507 Mon Sep 17 00:00:00 2001 From: Michael Niedermayer <michael@niedermayer.cc> Date: Sat, 9 Aug 2025 16:15:55 +0200 Subject: [PATCH] doc/developer: Basic documentation for Source Plugins Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> --- doc/developer.texi | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) diff --git a/doc/developer.texi b/doc/developer.texi index 10a2de00df..e346c7b57a 100644 --- a/doc/developer.texi +++ b/doc/developer.texi @@ -1142,4 +1142,36 @@ Publish the news entry. Send an announcement to the mailing list. @end enumerate +@anchor{Source Plugins} +@chapter Source Plugins + +@section What are Source Plugins + +Source plugins are a way to maintain features outside FFmpeg. + +Each is basically an automatically mergable git fork of FFmpeg. + +@section Checklist to be listed in merge-all-source-plugins + +@enumerate +@item +Supporting master and the latest release branch (with security fixes, when vulnerabilities are discovered) +Supporting older release branches is optional. + +@item +under LGPL or GPL license (that is a compatible Free software license) +and adds the needed dependancy to the --enable-gpl switch if its GPL. +@end enumerate + +@section How to make a Source Plugin + +To be automatically mergable it is important to keep all changes clean and well separated. +If you want to create a new source plugin, look at an existing one, or simply fork FFmpeg, +name the repository "sourceplugin-..." and add it to tools/merge-all-source-plugins +and try running it. Also check that it works with the latest releases. + +@section merge Source Plugins + +tools/merge-all-source-plugins + @bye -- 2.49.1 _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
reply other threads:[~2025-08-09 14:22 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20250809142232.473C668D0FE@ffbox0-bg.ffmpeg.org \ --to=code@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git