[FFmpeg-devel] [PATCH] Add tools/merge-all-source-plugins

[FFmpeg-devel] [PATCH] Add tools/merge-all-source-plugins

[Michael Niedermayer]

Simple script to merge all source plugins.

Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
---
 INSTALL.md                     | 3 +++
 tools/merge-all-source-plugins | 3 +++
 2 files changed, 6 insertions(+)
 create mode 100644 tools/merge-all-source-plugins

diff --git a/INSTALL.md b/INSTALL.md
index bdf58140149..0de204cef5b 100644
--- a/INSTALL.md
+++ b/INSTALL.md
@@ -1,5 +1,8 @@
 ## Installing FFmpeg
 
+0. If you like to include source plugins, merge them before configure
+for example run tools/merge-all-source-plugins
+
 1. Type `./configure` to create the configuration. A list of configure
 options is printed by running `configure --help`.
 
diff --git a/tools/merge-all-source-plugins b/tools/merge-all-source-plugins
new file mode 100644
index 00000000000..20764a07737
--- /dev/null
+++ b/tools/merge-all-source-plugins
@@ -0,0 +1,3 @@
+#!/bin/sh
+
+git pull --no-rebase --log --stat --commit --no-edit  https://github.com/michaelni/FFmpeg.git sourceplugin-libpostproc
-- 
2.49.0

_______________________________________________
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".

Re: [FFmpeg-devel] [PATCH] Add tools/merge-all-source-plugins

[Michael Niedermayer]

[-- Attachment #1.1: Type: text/plain, Size: 535 bytes --]

On Wed, May 14, 2025 at 12:55:09PM +0200, Michael Niedermayer wrote:
> Simple script to merge all source plugins.
> 
> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
> ---
>  INSTALL.md                     | 3 +++
>  tools/merge-all-source-plugins | 3 +++
>  2 files changed, 6 insertions(+)
>  create mode 100644 tools/merge-all-source-plugins

will apply

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

It is what and why we do it that matters, not just one of them.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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".

Re: [FFmpeg-devel] [PATCH] Add tools/merge-all-source-plugins

[Zhao Zhili]

> On May 14, 2025, at 18:55, Michael Niedermayer <michael@niedermayer.cc> wrote:
> 
> Simple script to merge all source plugins.

I think this is confusing. The operation of merging multiple branches can hardly be considered
a plugin.

> 
> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
> ---
> INSTALL.md                     | 3 +++
> tools/merge-all-source-plugins | 3 +++
> 2 files changed, 6 insertions(+)
> create mode 100644 tools/merge-all-source-plugins
> 
> diff --git a/INSTALL.md b/INSTALL.md
> index bdf58140149..0de204cef5b 100644
> --- a/INSTALL.md
> +++ b/INSTALL.md
> @@ -1,5 +1,8 @@
> ## Installing FFmpeg
> 
> +0. If you like to include source plugins, merge them before configure
> +for example run tools/merge-all-source-plugins
> +
> 1. Type `./configure` to create the configuration. A list of configure
> options is printed by running `configure --help`.
> 
> diff --git a/tools/merge-all-source-plugins b/tools/merge-all-source-plugins
> new file mode 100644
> index 00000000000..20764a07737
> --- /dev/null
> +++ b/tools/merge-all-source-plugins
> @@ -0,0 +1,3 @@
> +#!/bin/sh
> +
> +git pull --no-rebase --log --stat --commit --no-edit  https://github.com/michaelni/FFmpeg.git sourceplugin-libpostproc
> -- 
> 2.49.0
> 
> _______________________________________________
> 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".

_______________________________________________
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".

Re: [FFmpeg-devel] [PATCH] Add tools/merge-all-source-plugins

[Michael Niedermayer]

[-- Attachment #1.1: Type: text/plain, Size: 2760 bytes --]

Hi Zhao Zhili

On Thu, May 15, 2025 at 06:58:54PM +0800, Zhao Zhili wrote:
> 
> 
> > On May 14, 2025, at 18:55, Michael Niedermayer <michael@niedermayer.cc> wrote:
> > 
> > Simple script to merge all source plugins.
> 
> I think this is confusing. The operation of merging multiple branches can hardly be considered
> a plugin.

Each branch (well, there is just one ATM)

represents and contains exactly one plugin or you could also call it feature.
merging that branch integrates that feature / plugin.

Its a very simple system, it achives many of the goals people have
1. simple
2. easy to maintain
3. it does not allow binary blobs without source
4. it allows people to develop code under their own rules

Let me elaborate on 4.
    We are not a closed source company, people have the right to work on what
    they want to work on. I think 99% of us agree here

    Fact is, this does not work in ffmpeg-devel currently, several people have
    had their work rejected for non technical and non legal reasons.
    We could remove the most aggressive people, that would reduce this issue
    or we could support plugins (source plugins or classical plugins the details
    dont matter as long as developers can develop their code on their own terms
    and users can use them without censorship by someone)
    We also could change the development model to be like linux where this problem
    does not exist like this.

    So really, the way i think you should view plugins (and it could be a totally
    different implementation of teh concept of a plugin than this here)
    Is as a way to keep everyone in one team.
    If we cant give people a way to develop code externally and still have
    it accessible to users then we have to make it possible to develop
    it inside ffmpeg. Or we will loose many new developers who all want to
    develop something new and just cannot in this environment.

    That will lead to more conflicts and then the chance of people being kicked
    out or leaving will also go up. And if 2 people disagree, the one who wants
    to work should stay, and the one who wants to have a say in the work
    of the other should leave. Its the obvious way. A person working
    vs a person objecting to work. Which way will a project move forward ...

    I want to work, I want everyone else to be able to work, I want everyones
    work to be available to the end user.

thanks

PS: we can of course rename merge-all-source-plugins if someone has a better
name

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

If you think the mosad wants you dead since a long time then you are either
wrong or dead since a long time.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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".

Re: [FFmpeg-devel] [PATCH] Add tools/merge-all-source-plugins

[Zhao Zhili]

> On May 15, 2025, at 23:27, Michael Niedermayer <michael@niedermayer.cc> wrote:
> 
> Hi Zhao Zhili
> 
> On Thu, May 15, 2025 at 06:58:54PM +0800, Zhao Zhili wrote:
>> 
>> 
>>> On May 14, 2025, at 18:55, Michael Niedermayer <michael@niedermayer.cc> wrote:
>>> 
>>> Simple script to merge all source plugins.
>> 
>> I think this is confusing. The operation of merging multiple branches can hardly be considered
>> a plugin.
> 
> Each branch (well, there is just one ATM)
> 
> represents and contains exactly one plugin or you could also call it feature.
> merging that branch integrates that feature / plugin.
> 
> Its a very simple system, it achives many of the goals people have
> 1. simple
> 2. easy to maintain
> 3. it does not allow binary blobs without source
> 4. it allows people to develop code under their own rules

A plugin is accessories to the main project and cannot work independently on their own.
If I understand correctly, this strategy is working with other forks. A fork can merge other
forks as many as possible, and call itself the monolithic fork.

I want plugin support, mainly due to slow and hard building issues. Current strategy
doesn’t help in this case.

> 
> Let me elaborate on 4.
>    We are not a closed source company, people have the right to work on what
>    they want to work on. I think 99% of us agree here
> 
>    Fact is, this does not work in ffmpeg-devel currently, several people have
>    had their work rejected for non technical and non legal reasons.
>    We could remove the most aggressive people, that would reduce this issue
>    or we could support plugins (source plugins or classical plugins the details
>    dont matter as long as developers can develop their code on their own terms
>    and users can use them without censorship by someone)
>    We also could change the development model to be like linux where this problem
>    does not exist like this.
> 
>    So really, the way i think you should view plugins (and it could be a totally
>    different implementation of teh concept of a plugin than this here)
>    Is as a way to keep everyone in one team.
>    If we cant give people a way to develop code externally and still have
>    it accessible to users then we have to make it possible to develop
>    it inside ffmpeg. Or we will loose many new developers who all want to
>    develop something new and just cannot in this environment.
> 
>    That will lead to more conflicts and then the chance of people being kicked
>    out or leaving will also go up. And if 2 people disagree, the one who wants
>    to work should stay, and the one who wants to have a say in the work
>    of the other should leave. Its the obvious way. A person working
>    vs a person objecting to work. Which way will a project move forward ...
> 
>    I want to work, I want everyone else to be able to work, I want everyones
>    work to be available to the end user.
> 
> thanks
> 
> PS: we can of course rename merge-all-source-plugins if someone has a better
> name
> 
> [...]
> 
> -- 
> Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
> 
> If you think the mosad wants you dead since a long time then you are either
> wrong or dead since a long time.
> 
> _______________________________________________
> 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".
> 

_______________________________________________
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".

Re: [FFmpeg-devel] [PATCH] Add tools/merge-all-source-plugins

[softworkz .]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Michael
> Niedermayer
> Sent: Donnerstag, 15. Mai 2025 17:27
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] Add tools/merge-all-source-plugins
> 
> Hi Zhao Zhili
> 
> On Thu, May 15, 2025 at 06:58:54PM +0800, Zhao Zhili wrote:
> >
> >
> > > On May 14, 2025, at 18:55, Michael Niedermayer <michael@niedermayer.cc>
> wrote:
> > >
> > > Simple script to merge all source plugins.
> >
> > I think this is confusing. The operation of merging multiple branches can
> hardly be considered
> > a plugin.
> 
> Each branch (well, there is just one ATM)
> 
> represents and contains exactly one plugin or you could also call it feature.
> merging that branch integrates that feature / plugin.
> 
> Its a very simple system, it achives many of the goals people have
> 1. simple
> 2. easy to maintain
> 3. it does not allow binary blobs without source
> 4. it allows people to develop code under their own rules
> 
> Let me elaborate on 4.
>     We are not a closed source company, people have the right to work on what
>     they want to work on. I think 99% of us agree here
> 
>     Fact is, this does not work in ffmpeg-devel currently, several people have
>     had their work rejected for non technical and non legal reasons.
>     We could remove the most aggressive people, that would reduce this issue
>     or we could support plugins (source plugins or classical plugins the
> details
>     dont matter as long as developers can develop their code on their own
> terms
>     and users can use them without censorship by someone)
>     We also could change the development model to be like linux where this
> problem
>     does not exist like this.
> 
>     So really, the way i think you should view plugins (and it could be a
> totally
>     different implementation of teh concept of a plugin than this here)
>     Is as a way to keep everyone in one team.
>     If we cant give people a way to develop code externally and still have
>     it accessible to users then we have to make it possible to develop
>     it inside ffmpeg. Or we will loose many new developers who all want to
>     develop something new and just cannot in this environment.
> 
>     That will lead to more conflicts and then the chance of people being
> kicked
>     out or leaving will also go up. And if 2 people disagree, the one who
> wants
>     to work should stay, and the one who wants to have a say in the work
>     of the other should leave. 

Couldn't agree more!


> Its the obvious way. A person working
>     vs a person objecting to work. Which way will a project move forward ...
> 
>     I want to work, I want everyone else to be able to work, I want everyones
>     work to be available to the end user.

+1

Thanks,
softworkz


_______________________________________________
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".

Re: [FFmpeg-devel] [PATCH] Add tools/merge-all-source-plugins

[Rémi Denis-Courmont]

Hi,

Le 14 mai 2025 13:55:09 GMT+03:00, Michael Niedermayer <michael@niedermayer.cc> a écrit :
>Simple script to merge all source plugins.
>
>Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
>---
> INSTALL.md                     | 3 +++
> tools/merge-all-source-plugins | 3 +++
> 2 files changed, 6 insertions(+)
> create mode 100644 tools/merge-all-source-plugins
>
>diff --git a/INSTALL.md b/INSTALL.md
>index bdf58140149..0de204cef5b 100644
>--- a/INSTALL.md
>+++ b/INSTALL.md
>@@ -1,5 +1,8 @@
> ## Installing FFmpeg
> 
>+0. If you like to include source plugins, merge them before configure
>+for example run tools/merge-all-source-plugins
>+
> 1. Type `./configure` to create the configuration. A list of configure
> options is printed by running `configure --help`.
> 
>diff --git a/tools/merge-all-source-plugins b/tools/merge-all-source-plugins
>new file mode 100644
>index 00000000000..20764a07737
>--- /dev/null
>+++ b/tools/merge-all-source-plugins
>@@ -0,0 +1,3 @@
>+#!/bin/sh
>+
>+git pull --no-rebase --log --stat --commit --no-edit  https://github.com/michaelni/FFmpeg.git sourceplugin-libpostproc

I don't think the official Git repo should refer to an unofficial fork, no matter who the fork owner is (not to mention that not everyone here is comfortable with Github).
_______________________________________________
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".