From: Soft Works <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] GSoC 2025: Please review your Project Ideas lists
Date: Mon, 17 Feb 2025 03:31:36 +0000
Message-ID: <DM8P223MB0365DC18EF9D4CEE9AB9B0C9BAFB2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <tencent_30CECF8ED5792703B8A8960E4D48A028CD07@qq.com>
> -----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".
prev parent reply other threads:[~2025-02-17 3:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 19:28 [FFmpeg-devel] Fw: " Michael Niedermayer
2025-02-14 20:20 ` Kieran Kunhya via ffmpeg-devel
2025-02-14 20:30 ` Michael Niedermayer
2025-02-14 21:29 ` Steven Liu
2025-02-14 22:14 ` Kieran Kunhya via ffmpeg-devel
2025-02-14 23:30 ` Steven Liu
2025-02-15 15:06 ` Michael Niedermayer
2025-02-15 15:14 ` Michael Niedermayer
2025-02-15 15:41 ` Steven Liu
2025-02-16 2:47 ` Michael Niedermayer
2025-02-16 19:42 ` Soft Works
2025-02-17 0:25 ` Michael Niedermayer
2025-02-17 1:00 ` Soft Works
2025-02-17 2:36 ` [FFmpeg-devel] " Zhao Zhili
2025-02-17 3:31 ` Soft Works [this message]
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=DM8P223MB0365DC18EF9D4CEE9AB9B0C9BAFB2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz-at-hotmail.com@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