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

[Steven Liu <lingjiujianke@gmail.com>]

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