Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nuo Mi <nuomi2021@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] GSoC 2023
Date: Mon, 16 Jan 2023 21:53:10 +0800
Message-ID: <CAFXK13f5GSEmb_bsYV1piVcs918dFh86baeV+Gf2ugkb=e2cHw@mail.gmail.com> (raw)
In-Reply-To: <7dd5d18d-d4f6-4384-a55a-c4b200c81b62@mail.de>

On Mon, Jan 16, 2023 at 6:18 AM Thilo Borgmann <thilo.borgmann@mail.de>
wrote:

> Am 15.01.23 um 15:28 schrieb Nuo Mi:
> > On Sun, Jan 15, 2023 at 9:27 PM Ronald S. Bultje <rsbultje@gmail.com>
> wrote:
> >
> >> Hi,
> >>
> >> On Sun, Jan 15, 2023 at 4:20 AM Nuo Mi <nuomi2021@gmail.com> wrote:
> >>
> >>> Is it finalized?  Any chance to add some items in
> >>> https://github.com/ffvvc/FFmpeg/issues to the GSOC 2023?
> >>>
> >>
> >> It all depends on the student. And baseline ffvvc needs to be in already
> >> when the project starts. So it's not straightforward.
>
> Yet we are openand can add project proposals before the application
> deadline (Feb. 7th).
> Do not wait until the last day, especially that having VVC yet in review
> does not make it easier to describe/define.
> The project needs to extend the decoder, mere upstreaming should not be
> enough IIUC.
> Also yes, it is highly preferable to have something upstream before
> project start end of Mai.
>
>
> >> Are you proposing to be the student? Or what's your plan?
> >>
> > I am not so young. :)
> > Just want to get more exposure and resources to prepare a decent version
> > upstream.
>
> Most importantly define a valid project and find a mentor with the time
> and abilities needed.
> Having a (co-)mentor is also especially if you want to mentor it yourself.
>
> -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 and Ronald,
Thank you for the detailed information.
Seems too hurried for this time.  Maybe next time
Or everything is smooth, we do need GSOC 2024 for VVC decoder :)
_______________________________________________
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".

  reply	other threads:[~2023-01-16 13:53 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 [this message]
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
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='CAFXK13f5GSEmb_bsYV1piVcs918dFh86baeV+Gf2ugkb=e2cHw@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