From: Nuo Mi <nuomi2021@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] GSoC 2023
Date: Tue, 24 Jan 2023 21:16:21 +0800
Message-ID: <CAFXK13c0qNEvuFb=zbzYTVGOMfHqhRya8LynMm7suBQasLHQ-w@mail.gmail.com> (raw)
In-Reply-To: <9eed215f-31b2-0f0c-19eb-0f8f4b73dee3@mail.de>
On Mon, Jan 23, 2023 at 6:50 PM Thilo Borgmann <thilo.borgmann@mail.de>
wrote:
> Hi,
>
> sorry for delay, some thoughts:
>
> > Description: VVC is the successor to the well-known codec HEVC. The whole
> > video industry has high anticipation for VVC. The goal of the ffvvc
> > project is to provide a VVC decoder for FFmpeg. We invite you to join us
> in> improving ffvvc. Depending on your background, you will help add
> > ALF/SAO/Predict assembly code or new features/tests for ffvvc.
> > Expected results: 500+ lines of code merged into the ffvvc project.
>
> The "We invite you..." sentence seems out of... our evil strictly
> technical style.
>
> I would avoid a background discussion and project definition talk with an
> interested student.
> Better do offer two distinct project ideas, one for assembly opts and one
> for features/tests.
> Possibly you could also split the testing into even a third project and
> make it the smallest project duration.
> It might even be extended to add tests in general... just VVC as the first
> to do.
>
> Also, we could only ask for one slot per project idea (which is meant to
> be taken by one individual).
> Means if you got more than one interested & capable students, you could
> not accept more than one.
>
>
> > Prerequisites: Good C and Assembly code, basic familiarity with Git, and
> > knowledge of codecs.
> >
> > Difficulty: Hard
> >
> > Qualification Task: Fix any issue on
> https://github.com/ffvvc/FFmpeg/issues
> > or any patch merged by ffvvc.
> >
> > Mentor: Nuo Mi (nuomi2021 at gmail dot com)
> >
> > Duration: 350 hours
>
>
> > Hi All,
> > It's more than welcome if somebody can do the co-mentor. Please reply to
> > this if you are interested.
>
> This part will hardly be recognized by many, maybe sent another mail for
> that.
> It might be faster to ask once or twice on ffmpeg-devel IRC.
>
> For a testing project, you can add me as backup mentor.
> For the opts & features I would prefer someone else to do it - although I
> will if nobody else can be found.
>
> -Thilo
> _______________________________________________
> 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".
>
Hi Thilo,
No worries.Especially when you have so detailed suggestions
Updated on https://trac.ffmpeg.org/wiki/SponsoringPrograms/GSoC/2023
Feel free to change it if something is not correct.
I ping IRC for backup mentors.
Thank you very much.
_______________________________________________
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".
next prev parent reply other threads:[~2023-01-24 13:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 14:42 Thilo Borgmann
2022-12-15 14:47 ` Jean-Baptiste Kempf
2022-12-15 22:47 ` Pierre-Anthony Lemieux
2022-12-18 16:47 ` Thilo Borgmann
2023-01-15 9:20 ` Nuo Mi
2023-01-15 13:26 ` Ronald S. Bultje
2023-01-15 13:56 ` Jean-Baptiste Kempf
2023-01-15 14:31 ` Nuo Mi
2023-01-15 14:28 ` Nuo Mi
2023-01-15 22:18 ` Thilo Borgmann
2023-01-16 13:53 ` Nuo Mi
2023-01-16 14:58 ` Jean-Baptiste Kempf
2023-01-17 15:22 ` Nuo Mi
2023-01-19 11:10 ` Nuo Mi
2023-01-23 10:50 ` Thilo Borgmann
2023-01-24 13:16 ` Nuo Mi [this message]
2023-02-23 19:27 ` Thilo Borgmann
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='CAFXK13c0qNEvuFb=zbzYTVGOMfHqhRya8LynMm7suBQasLHQ-w@mail.gmail.com' \
--to=nuomi2021@gmail.com \
--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