[FFmpeg-devel] Fw: GSoC 2025: Please review your Project Ideas lists

[FFmpeg-devel] Fw: GSoC 2025: Please review your Project Ideas lists

[Michael Niedermayer]

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

Hi everyone

Please help improve the gsoc 2025 page

2 ideas are missing backup mentors, if you are able please
add yourself to them as backup mentor

Also please add more ideas!
And help review the page and ideas to ensure it is all in good shape.

thx

----- Forwarded message from summerofcode-noreply@google.com -----

Date: Thu, 13 Feb 2025 20:38:55 -0800
From: summerofcode-noreply@google.com
To: michael@niedermayer.cc
Subject: GSoC 2025: Please review your Project Ideas lists

Google Summer of Code


Hello,

We are carefully reviewing the 2025 GSoC Org applications and are discovering an alarming number of orgs with only a couple of ideas or ideas that haven't been updated since 2023 or 2024. Please make sure your project ideas are all in your lists NOW, we can only review what is there and if you have an incomplete list you risk your org being rejected this year.

We have more people on our review team than ever before and are taking a very close look at all applications this year, including individual ideas and discovering quite a few that are way overscoped for GSoC and even a few that are inappropriate ideas for the program. Please review your lists, Org Admins it is your responsibility to be sure the Project Ideas represent your org appropriately.

Best,

Stephanie Taylor

GSoC Program Lead




https://summerofcode.withgoogle.com

For any questions, please contact gsoc-support@google.com. Replies to this message go to an unmonitored mailbox.

© 2025 Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA







----- End forwarded message -----

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

In a rich man's house there is no place to spit but his face.
-- Diogenes of Sinope

[-- 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] Fw: GSoC 2025: Please review your Project Ideas lists

[Kieran Kunhya via ffmpeg-devel]

On Fri, Feb 14, 2025 at 7:28 PM Michael Niedermayer
<michael@niedermayer.cc> wrote:
>
> Hi everyone
>
> Please help improve the gsoc 2025 page
>
> 2 ideas are missing backup mentors, if you are able please
> add yourself to them as backup mentor
>
> Also please add more ideas!
> And help review the page and ideas to ensure it is all in good shape.
>
> thx
>
> ----- Forwarded message from summerofcode-noreply@google.com -----
>
> Date: Thu, 13 Feb 2025 20:38:55 -0800
> From: summerofcode-noreply@google.com
> To: michael@niedermayer.cc
> Subject: GSoC 2025: Please review your Project Ideas lists
>
> Google Summer of Code
>
>
> Hello,
>
> We are carefully reviewing the 2025 GSoC Org applications and are discovering an alarming number of orgs with only a couple of ideas or ideas that haven't been updated since 2023 or 2024. Please make sure your project ideas are all in your lists NOW, we can only review what is there and if you have an incomplete list you risk your org being rejected this year.
>
> We have more people on our review team than ever before and are taking a very close look at all applications this year, including individual ideas and discovering quite a few that are way overscoped for GSoC and even a few that are inappropriate ideas for the program. Please review your lists, Org Admins it is your responsibility to be sure the Project Ideas represent your org appropriately.

The WHIP one is obviously way too overscoped and challenging for a student.

Kieran
_______________________________________________
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] Fw: GSoC 2025: Please review your Project Ideas lists

[Michael Niedermayer]

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

Hi

CCing Steven (Mentor of WHIP) and Zhao Jun (Backup Mentor of WHIP)

On Fri, Feb 14, 2025 at 08:20:51PM +0000, Kieran Kunhya via ffmpeg-devel wrote:
> On Fri, Feb 14, 2025 at 7:28 PM Michael Niedermayer
> <michael@niedermayer.cc> wrote:
> >
> > Hi everyone
> >
> > Please help improve the gsoc 2025 page
> >
> > 2 ideas are missing backup mentors, if you are able please
> > add yourself to them as backup mentor
> >
> > Also please add more ideas!
> > And help review the page and ideas to ensure it is all in good shape.
> >
> > thx
> >
> > ----- Forwarded message from summerofcode-noreply@google.com -----
> >
> > Date: Thu, 13 Feb 2025 20:38:55 -0800
> > From: summerofcode-noreply@google.com
> > To: michael@niedermayer.cc
> > Subject: GSoC 2025: Please review your Project Ideas lists
> >
> > Google Summer of Code
> >
> >
> > Hello,
> >
> > We are carefully reviewing the 2025 GSoC Org applications and are discovering an alarming number of orgs with only a couple of ideas or ideas that haven't been updated since 2023 or 2024. Please make sure your project ideas are all in your lists NOW, we can only review what is there and if you have an incomplete list you risk your org being rejected this year.
> >
> > We have more people on our review team than ever before and are taking a very close look at all applications this year, including individual ideas and discovering quite a few that are way overscoped for GSoC and even a few that are inappropriate ideas for the program. Please review your lists, Org Admins it is your responsibility to be sure the Project Ideas represent your org appropriately.
> 
> The WHIP one is obviously way too overscoped and challenging for a student.
>
> Kieran
> _______________________________________________
> 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".

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

If you fake or manipulate statistics in a paper in physics you will never
get a job again.
If you fake or manipulate statistics in a paper in medicin you will get
a job for life at the pharma industry.

[-- 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] Fw: GSoC 2025: Please review your Project Ideas lists

[Steven Liu]

Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>于2025年2月15日
周六04:21写道：

> On Fri, Feb 14, 2025 at 7:28 PM Michael Niedermayer
> <michael@niedermayer.cc> wrote:
> >
> > Hi everyone
> >
> > Please help improve the gsoc 2025 page
> >
> > 2 ideas are missing backup mentors, if you are able please
> > add yourself to them as backup mentor
> >
> > Also please add more ideas!
> > And help review the page and ideas to ensure it is all in good shape.
> >
> > thx
> >
> > ----- Forwarded message from summerofcode-noreply@google.com -----
> >
> > Date: Thu, 13 Feb 2025 20:38:55 -0800
> > From: summerofcode-noreply@google.com
> > To: michael@niedermayer.cc
> > Subject: GSoC 2025: Please review your Project Ideas lists
> >
> > Google Summer of Code
> >
> >
> > Hello,
> >
> > We are carefully reviewing the 2025 GSoC Org applications and are
> discovering an alarming number of orgs with only a couple of ideas or ideas
> that haven't been updated since 2023 or 2024. Please make sure your project
> ideas are all in your lists NOW, we can only review what is there and if
> you have an incomplete list you risk your org being rejected this year.
> >
> > We have more people on our review team than ever before and are taking a
> very close look at all applications this year, including individual ideas
> and discovering quite a few that are way overscoped for GSoC and even a few
> that are inappropriate ideas for the program. Please review your lists, Org
> Admins it is your responsibility to be sure the Project Ideas represent
> your org appropriately.
>
> The WHIP one is obviously way too overscoped and challenging for a student.

Hi Kieran,

    There have many references projects implementation that,
https://obsproject.com/kb/whip-streaming-guide
And gst.

And there have lots of implementation code about in ffmpeg but not
submitted to ffmpeg, I think I can guide students do it.

Thanks for your focusing and I think it would be successful in GSoC
Timeline and I think you will give more details advice when students
implementing WHIP, of course that will more nice if you can be a mentor to
WHIP.😄


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

Thanks
Steven
_______________________________________________
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] Fw: GSoC 2025: Please review your Project Ideas lists

[Kieran Kunhya via ffmpeg-devel]

On Fri, 14 Feb 2025, 21:29 Steven Liu, <lingjiujianke@gmail.com> wrote:

>
>
> Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>于2025年2月15日
> 周六04:21写道：
>
>> On Fri, Feb 14, 2025 at 7:28 PM Michael Niedermayer
>> <michael@niedermayer.cc> wrote:
>> >
>> > Hi everyone
>> >
>> > Please help improve the gsoc 2025 page
>> >
>> > 2 ideas are missing backup mentors, if you are able please
>> > add yourself to them as backup mentor
>> >
>> > Also please add more ideas!
>> > And help review the page and ideas to ensure it is all in good shape.
>> >
>> > thx
>> >
>> > ----- Forwarded message from summerofcode-noreply@google.com -----
>> >
>> > Date: Thu, 13 Feb 2025 20:38:55 -0800
>> > From: summerofcode-noreply@google.com
>> > To: michael@niedermayer.cc
>> > Subject: GSoC 2025: Please review your Project Ideas lists
>> >
>> > Google Summer of Code
>> >
>> >
>> > Hello,
>> >
>> > We are carefully reviewing the 2025 GSoC Org applications and are
>> discovering an alarming number of orgs with only a couple of ideas or ideas
>> that haven't been updated since 2023 or 2024. Please make sure your project
>> ideas are all in your lists NOW, we can only review what is there and if
>> you have an incomplete list you risk your org being rejected this year.
>> >
>> > We have more people on our review team than ever before and are taking
>> a very close look at all applications this year, including individual ideas
>> and discovering quite a few that are way overscoped for GSoC and even a few
>> that are inappropriate ideas for the program. Please review your lists, Org
>> Admins it is your responsibility to be sure the Project Ideas represent
>> your org appropriately.
>>
>> The WHIP one is obviously way too overscoped and challenging for a
>> student.
>
> Hi Kieran,
>
>     There have many references projects implementation that,
> https://obsproject.com/kb/whip-streaming-guide
> And gst.
>
> And there have lots of implementation code about in ffmpeg but not
> submitted to ffmpeg, I think I can guide students do it.
>
> Thanks for your focusing and I think it would be successful in GSoC
> Timeline and I think you will give more details advice when students
> implementing WHIP, of course that will more nice if you can be a mentor to
> WHIP.😄
>
>
>> Kieran
>> _______________________________________________
>> 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".
>>
>
> Thanks
> Steven
>
>
Hi Steven,

WebRTC is a very complex protocol and even more difficult to implement in
FFmpeg (owing to lack of event loop).

Could you potentially constrain the project to a small subset? It clearly
is a lot more than 359 hours of work.

Regards,
Kieran Kunhya
_______________________________________________
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] Fw: GSoC 2025: Please review your Project Ideas lists

[Steven Liu]

Kieran Kunhya <kieran618@googlemail.com>于2025年2月15日 周六06:15写道：

>
>
> On Fri, 14 Feb 2025, 21:29 Steven Liu, <lingjiujianke@gmail.com> wrote:
>
>>
>>
>> Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>于2025年2月15日
>> 周六04:21写道：
>>
>>> On Fri, Feb 14, 2025 at 7:28 PM Michael Niedermayer
>>> <michael@niedermayer.cc> wrote:
>>> >
>>> > Hi everyone
>>> >
>>> > Please help improve the gsoc 2025 page
>>> >
>>> > 2 ideas are missing backup mentors, if you are able please
>>> > add yourself to them as backup mentor
>>> >
>>> > Also please add more ideas!
>>> > And help review the page and ideas to ensure it is all in good shape.
>>> >
>>> > thx
>>> >
>>> > ----- Forwarded message from summerofcode-noreply@google.com -----
>>> >
>>> > Date: Thu, 13 Feb 2025 20:38:55 -0800
>>> > From: summerofcode-noreply@google.com
>>> > To: michael@niedermayer.cc
>>> > Subject: GSoC 2025: Please review your Project Ideas lists
>>> >
>>> > Google Summer of Code
>>> >
>>> >
>>> > Hello,
>>> >
>>> > We are carefully reviewing the 2025 GSoC Org applications and are
>>> discovering an alarming number of orgs with only a couple of ideas or ideas
>>> that haven't been updated since 2023 or 2024. Please make sure your project
>>> ideas are all in your lists NOW, we can only review what is there and if
>>> you have an incomplete list you risk your org being rejected this year.
>>> >
>>> > We have more people on our review team than ever before and are taking
>>> a very close look at all applications this year, including individual ideas
>>> and discovering quite a few that are way overscoped for GSoC and even a few
>>> that are inappropriate ideas for the program. Please review your lists, Org
>>> Admins it is your responsibility to be sure the Project Ideas represent
>>> your org appropriately.
>>>
>>> The WHIP one is obviously way too overscoped and challenging for a
>>> student.
>>
>> Hi Kieran,
>>
>>     There have many references projects implementation that,
>> https://obsproject.com/kb/whip-streaming-guide
>> And gst.
>>
>> And there have lots of implementation code about in ffmpeg but not
>> submitted to ffmpeg, I think I can guide students do it.
>>
>> Thanks for your focusing and I think it would be successful in GSoC
>> Timeline and I think you will give more details advice when students
>> implementing WHIP, of course that will more nice if you can be a mentor to
>> WHIP.😄
>>
>>
>>> Kieran
>>> _______________________________________________
>>> 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".
>>>
>>
>> Thanks
>> Steven
>>
>>
> Hi Steven,
>
> WebRTC is a very complex protocol and even more difficult to implement in
> FFmpeg (owing to lack of event loop).
>
> Could you potentially constrain the project to a small subset? It clearly
> is a lot more than 359 hours of work.
>
That’s not whole WebRTC, just push streams to server, we can implement a
tiny function, I know WebRTC is too huge and there have lots of algorithms
geek want injection their selves algorithms, I think we should just
implement a smaller WHIP is ok, let stream publish users have more choose,
there should not only rtmp can push streams.
Let try do that. Not need implement full and perfect functions, just can
push streams by WHIP is ok.

>
> Regards,
> Kieran Kunhya
>


Thanks Kieran

Steven

>
_______________________________________________
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] Fw: GSoC 2025: Please review your Project Ideas lists

[Michael Niedermayer]

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

Hi Steven

On Sat, Feb 15, 2025 at 07:30:40AM +0800, Steven Liu wrote:
> Kieran Kunhya <kieran618@googlemail.com>于2025年2月15日 周六06:15写道：
> 
> >
> >
> > On Fri, 14 Feb 2025, 21:29 Steven Liu, <lingjiujianke@gmail.com> wrote:
> >
> >>
> >>
> >> Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>于2025年2月15日
> >> 周六04:21写道：
> >>
> >>> On Fri, Feb 14, 2025 at 7:28 PM Michael Niedermayer
> >>> <michael@niedermayer.cc> wrote:
> >>> >
> >>> > Hi everyone
> >>> >
> >>> > Please help improve the gsoc 2025 page
> >>> >
> >>> > 2 ideas are missing backup mentors, if you are able please
> >>> > add yourself to them as backup mentor
> >>> >
> >>> > Also please add more ideas!
> >>> > And help review the page and ideas to ensure it is all in good shape.
> >>> >
> >>> > thx
> >>> >
> >>> > ----- Forwarded message from summerofcode-noreply@google.com -----
> >>> >
> >>> > Date: Thu, 13 Feb 2025 20:38:55 -0800
> >>> > From: summerofcode-noreply@google.com
> >>> > To: michael@niedermayer.cc
> >>> > Subject: GSoC 2025: Please review your Project Ideas lists
> >>> >
> >>> > Google Summer of Code
> >>> >
> >>> >
> >>> > Hello,
> >>> >
> >>> > We are carefully reviewing the 2025 GSoC Org applications and are
> >>> discovering an alarming number of orgs with only a couple of ideas or ideas
> >>> that haven't been updated since 2023 or 2024. Please make sure your project
> >>> ideas are all in your lists NOW, we can only review what is there and if
> >>> you have an incomplete list you risk your org being rejected this year.
> >>> >
> >>> > We have more people on our review team than ever before and are taking
> >>> a very close look at all applications this year, including individual ideas
> >>> and discovering quite a few that are way overscoped for GSoC and even a few
> >>> that are inappropriate ideas for the program. Please review your lists, Org
> >>> Admins it is your responsibility to be sure the Project Ideas represent
> >>> your org appropriately.
> >>>
> >>> The WHIP one is obviously way too overscoped and challenging for a
> >>> student.
> >>
> >> Hi Kieran,
> >>
> >>     There have many references projects implementation that,
> >> https://obsproject.com/kb/whip-streaming-guide
> >> And gst.
> >>
> >> And there have lots of implementation code about in ffmpeg but not
> >> submitted to ffmpeg, I think I can guide students do it.
> >>
> >> Thanks for your focusing and I think it would be successful in GSoC
> >> Timeline and I think you will give more details advice when students
> >> implementing WHIP, of course that will more nice if you can be a mentor to
> >> WHIP.😄
> >>
> >>
> >>> Kieran
> >>> _______________________________________________
> >>> 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".
> >>>
> >>
> >> Thanks
> >> Steven
> >>
> >>
> > Hi Steven,
> >
> > WebRTC is a very complex protocol and even more difficult to implement in
> > FFmpeg (owing to lack of event loop).
> >
> > Could you potentially constrain the project to a small subset? It clearly
> > is a lot more than 359 hours of work.
> >

> That’s not whole WebRTC, just push streams to server, we can implement a
> tiny function, I know WebRTC is too huge and there have lots of algorithms
> geek want injection their selves algorithms, I think we should just
> implement a smaller WHIP is ok, let stream publish users have more choose,
> there should not only rtmp can push streams.
> Let try do that. Not need implement full and perfect functions, just can
> push streams by WHIP is ok.

you can also split it in 2 or more ideas, if that makes sense.
But please clarify the text on the ideas page so its clear, what it is about.

You can also run the text through chatgpt and ask for it to correct the
english grammer (but check if its still correct after that)

thx

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

z(9) = an object that transcends all computable functions describable
in finite terms. - ChatGPT in 2024

[-- 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] Fw: GSoC 2025: Please review your Project Ideas lists

[Michael Niedermayer]

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

Hi Steven

On Sat, Feb 15, 2025 at 07:30:40AM +0800, Steven Liu wrote:
[...]
> That’s not whole WebRTC, just push streams to server, we can implement a
> tiny function, I know WebRTC is too huge and there have lots of algorithms
> geek want injection their selves algorithms, I think we should just
> implement a smaller WHIP is ok, let stream publish users have more choose,
> there should not only rtmp can push streams.
> Let try do that. Not need implement full and perfect functions, just can
> push streams by WHIP is ok.

Also the long list of RFCs looks like the student would have to learn/understand
all of them.
If the tiny part the students project is about only needs a subset then its
better to list only what is needed.

thx

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

No human being will ever know the Truth, for even if they happen to say it
by chance, they would not even known they had done so. -- Xenophanes

[-- 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] Fw: GSoC 2025: Please review your Project Ideas lists

[Steven Liu]

Michael Niedermayer <michael@niedermayer.cc> 于2025年2月15日周六 23:14写道：
>
> Hi Steven
>
> On Sat, Feb 15, 2025 at 07:30:40AM +0800, Steven Liu wrote:
> [...]
> > That’s not whole WebRTC, just push streams to server, we can implement a
> > tiny function, I know WebRTC is too huge and there have lots of algorithms
> > geek want injection their selves algorithms, I think we should just
> > implement a smaller WHIP is ok, let stream publish users have more choose,
> > there should not only rtmp can push streams.
> > Let try do that. Not need implement full and perfect functions, just can
> > push streams by WHIP is ok.
>
> Also the long list of RFCs looks like the student would have to learn/understand
> all of them.
> If the tiny part the students project is about only needs a subset then its
> better to list only what is needed.
Hi Kieran and Michael,

Ok, Based on Michael and Kieran's suggestions, some changes have been
made. Could you please review whether the current description is now
concise enough?


Thanks
Steven
_______________________________________________
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] Fw: GSoC 2025: Please review your Project Ideas lists

[Michael Niedermayer]

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

Hi Steven

On Sat, Feb 15, 2025 at 11:41:46PM +0800, Steven Liu wrote:
> Michael Niedermayer <michael@niedermayer.cc> 于2025年2月15日周六 23:14写道：
> >
> > Hi Steven
> >
> > On Sat, Feb 15, 2025 at 07:30:40AM +0800, Steven Liu wrote:
> > [...]
> > > That’s not whole WebRTC, just push streams to server, we can implement a
> > > tiny function, I know WebRTC is too huge and there have lots of algorithms
> > > geek want injection their selves algorithms, I think we should just
> > > implement a smaller WHIP is ok, let stream publish users have more choose,
> > > there should not only rtmp can push streams.
> > > Let try do that. Not need implement full and perfect functions, just can
> > > push streams by WHIP is ok.
> >
> > Also the long list of RFCs looks like the student would have to learn/understand
> > all of them.
> > If the tiny part the students project is about only needs a subset then its
> > better to list only what is needed.
> Hi Kieran and Michael,
> 
> Ok, Based on Michael and Kieran's suggestions, some changes have been
> made. Could you please review whether the current description is now
> concise enough?

Given that i dont know WHIP, and that iam not a native english speaker
I think there are many other people better suited on this mailing list
to review this text.

But to me it sounds fine

thx

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

No great genius has ever existed without some touch of madness. -- Aristotle

[-- 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] Fw: GSoC 2025: Please review your Project Ideas lists

[Soft Works]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Michael Niedermayer
> Sent: Freitag, 14. Februar 2025 20:29
> To: FFmpeg development discussions and patches <ffmpeg-
> devel@ffmpeg.org>
> Subject: [FFmpeg-devel] Fw: GSoC 2025: Please review your Project Ideas lists
> 
> Hi everyone
> 
> Please help improve the gsoc 2025 page
> 
> 2 ideas are missing backup mentors, if you are able please
> add yourself to them as backup mentor
> 
> Also please add more ideas!

Hi Michael,

would this be a valid gsoc project?


- Develop a scraping tool which iterates ffmpeg forks on GitHub, investigates 
  branches and identifies patches which don't exist in upstream ffmpeg
- Deduplicate results
- Setup a customized AI with knowledge about the ffmpeg source code
- Run this AI to classify the results:
  - feature or fix
  - generally valid or just special cake
  - value for the project
- Finally filter and produce a list of high-value patches which are worth looking at

I believe there are many good and valuable patches out there, which never made
It into ffmpeg because developers didn't want to go through the submission
Procedures.

sw




_______________________________________________
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] Fw: GSoC 2025: Please review your Project Ideas lists

[Michael Niedermayer]

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

Hi Soft Works

On Sun, Feb 16, 2025 at 07:42:11PM +0000, Soft Works wrote:
> 
> 
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> > Michael Niedermayer
> > Sent: Freitag, 14. Februar 2025 20:29
> > To: FFmpeg development discussions and patches <ffmpeg-
> > devel@ffmpeg.org>
> > Subject: [FFmpeg-devel] Fw: GSoC 2025: Please review your Project Ideas lists
> > 
> > Hi everyone
> > 
> > Please help improve the gsoc 2025 page
> > 
> > 2 ideas are missing backup mentors, if you are able please
> > add yourself to them as backup mentor
> > 
> > Also please add more ideas!
> 
> Hi Michael,
> 
> would this be a valid gsoc project?
> 
> 
> - Develop a scraping tool which iterates ffmpeg forks on GitHub, investigates 
>   branches and identifies patches which don't exist in upstream ffmpeg
> - Deduplicate results
> - Setup a customized AI with knowledge about the ffmpeg source code
> - Run this AI to classify the results:
>   - feature or fix
>   - generally valid or just special cake
>   - value for the project
> - Finally filter and produce a list of high-value patches which are worth looking at
> 
> I believe there are many good and valuable patches out there, which never made
> It into ffmpeg because developers didn't want to go through the submission
> Procedures.

My personal oppinion is that this is a great idea. And that it would be
valuable for FFmpeg.
If you checked teh GSoC rules and the community has no objections
against it then it should be ok

maybe reword the "customized AI" so that its clear that this could be
something simple like just asking chatgpt to clasify commit messages.
So it doesnt look like this would require building/training a new model
from scratch. (as google complained about over speced tasks)

thx

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

If you drop bombs on a foreign country and kill a hundred thousand
innocent people, expect your government to call the consequence
"unprovoked inhuman terrorist attacks" and use it to justify dropping
more bombs and killing more people. The technology changed, the idea is old.

[-- 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] Fw: GSoC 2025: Please review your Project Ideas lists

[Soft Works]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Michael Niedermayer
> Sent: Montag, 17. Februar 2025 01:25
> To: FFmpeg development discussions and patches <ffmpeg-
> devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Fw: GSoC 2025: Please review your Project Ideas
> lists
> 
> Hi Soft Works
> 
> On Sun, Feb 16, 2025 at 07:42:11PM +0000, Soft Works wrote:
> >
> >
> > > -----Original Message-----
> > > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> > > Michael Niedermayer
> > > Sent: Freitag, 14. Februar 2025 20:29
> > > To: FFmpeg development discussions and patches <ffmpeg-
> > > devel@ffmpeg.org>
> > > Subject: [FFmpeg-devel] Fw: GSoC 2025: Please review your Project Ideas
> lists
> > >
> > > Hi everyone
> > >
> > > Please help improve the gsoc 2025 page
> > >
> > > 2 ideas are missing backup mentors, if you are able please
> > > add yourself to them as backup mentor
> > >
> > > Also please add more ideas!
> >
> > Hi Michael,
> >
> > would this be a valid gsoc project?
> >
> >
> > - Develop a scraping tool which iterates ffmpeg forks on GitHub, investigates
> >   branches and identifies patches which don't exist in upstream ffmpeg
> > - Deduplicate results
> > - Setup a customized AI with knowledge about the ffmpeg source code
> > - Run this AI to classify the results:
> >   - feature or fix
> >   - generally valid or just special cake
> >   - value for the project
> > - Finally filter and produce a list of high-value patches which are worth
> looking at
> >
> > I believe there are many good and valuable patches out there, which never
> made
> > It into ffmpeg because developers didn't want to go through the submission
> > Procedures.
> 
> My personal oppinion is that this is a great idea. And that it would be
> valuable for FFmpeg.
> If you checked teh GSoC rules and the community has no objections
> against it then it should be ok

TBH, I didn't check anything and I don't know much about GSoC. This is just an idea that I was carrying around for a while (waiting for the right moment to drop it 😊 )

> maybe reword the "customized AI" so that its clear that this could be
> something simple like just asking chatgpt to clasify commit messages.
> So it doesnt look like this would require building/training a new model
> from scratch. (as google complained about over speced tasks)

(What are speced tasks?)

I would make it that easy. What I had in mind when with "customized AI" was preparing the ffmpeg code file as "embeddings" (in a vector format). This makes it available to the model without being part of the input. 
How effective that would be  - I don't know, but I'm very curious about finding out.
Another option would be to at least perform a "casting" of models to find out which is most familiar with ffmpeg.

Should this work well, a follow-up project might be to build an automated pull request validation based on that.
Not that it would be required, things are always reviewed very carefully and critically, but it might find obvious things without anybody needing to spend time on it and it would give feedback to submitters early.

sw





_______________________________________________
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] GSoC 2025: Please review your Project Ideas lists

[Zhao Zhili]

> On Feb 17, 2025, at 03:42, Soft Works <softworkz-at-hotmail.com@ffmpeg.org> wrote:
> 
> 
>> -----Original Message-----
>> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
>> Michael Niedermayer
>> Sent: Freitag, 14. Februar 2025 20:29
>> To: FFmpeg development discussions and patches <ffmpeg-
>> devel@ffmpeg.org>
>> Subject: [FFmpeg-devel] Fw: GSoC 2025: Please review your Project Ideas lists
>> 
>> Hi everyone
>> 
>> Please help improve the gsoc 2025 page
>> 
>> 2 ideas are missing backup mentors, if you are able please
>> add yourself to them as backup mentor
>> 
>> Also please add more ideas!
> 
> Hi Michael,
> 
> would this be a valid gsoc project?
> 
> 
> - Develop a scraping tool which iterates ffmpeg forks on GitHub, investigates 
>  branches and identifies patches which don't exist in upstream ffmpeg
> - Deduplicate results
> - Setup a customized AI with knowledge about the ffmpeg source code
> - Run this AI to classify the results:
>  - feature or fix
>  - generally valid or just special cake
>  - value for the project
> - Finally filter and produce a list of high-value patches which are worth looking at
> 
> I believe there are many good and valuable patches out there, which never made
> It into ffmpeg because developers didn't want to go through the submission
> Procedures.

I think mentor should know what to do and how to do it exactly (maybe with some
details missing) for a GSoC project. An experimental idea without confidence in
feasibility leave the student in a dangerous situation.

> 
> sw
> 
> 
> 
> 
> _______________________________________________
> 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] GSoC 2025: Please review your Project Ideas lists

[Soft Works]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Zhao
> Zhili
> Sent: Montag, 17. Februar 2025 03:36
> To: FFmpeg development discussions and patches <ffmpeg-
> devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] GSoC 2025: Please review your Project Ideas lists
> 
> 
> 
> > On Feb 17, 2025, at 03:42, Soft Works <softworkz-at-
> hotmail.com@ffmpeg.org> wrote:
> >
> >
> >> -----Original Message-----
> >> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> >> Michael Niedermayer
> >> Sent: Freitag, 14. Februar 2025 20:29
> >> To: FFmpeg development discussions and patches <ffmpeg-
> >> devel@ffmpeg.org>
> >> Subject: [FFmpeg-devel] Fw: GSoC 2025: Please review your Project Ideas
> lists
> >>
> >> Hi everyone
> >>
> >> Please help improve the gsoc 2025 page
> >>
> >> 2 ideas are missing backup mentors, if you are able please
> >> add yourself to them as backup mentor
> >>
> >> Also please add more ideas!
> >
> > Hi Michael,
> >
> > would this be a valid gsoc project?
> >
> >
> > - Develop a scraping tool which iterates ffmpeg forks on GitHub, investigates
> >  branches and identifies patches which don't exist in upstream ffmpeg
> > - Deduplicate results
> > - Setup a customized AI with knowledge about the ffmpeg source code
> > - Run this AI to classify the results:
> >  - feature or fix
> >  - generally valid or just special cake
> >  - value for the project
> > - Finally filter and produce a list of high-value patches which are worth
> looking at
> >
> > I believe there are many good and valuable patches out there, which never
> made
> > It into ffmpeg because developers didn't want to go through the submission
> > Procedures.
> 
> I think mentor should know what to do and how to do it exactly (maybe with
> some
> details missing) for a GSoC project. An experimental idea without confidence in
> feasibility leave the student in a dangerous situation.

Hi Zhao,

There are about 12k forks of ffmpeg at the moment on GitHub and I've come across a number of good things over the years without looking for any. I am confident that when doing it myself, I'd get useful results, even though I cannot exactly predict quantity and quality. 
Yet - it might require to adapt the strategy details at some points and evaluate the best ways for proceeding.
In this regard, it is not of the kind where I know in every detail how the end result will be and how it will be achieved - like projects that you've already finished in your head, just not done yet.
So yeah, if it's gotta be something like the latter, then it's probably not suitable.

Thanks
sw







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