From: Thilo Borgmann <thilo.borgmann@mail.de>
To: FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>,
"Google Sumer of code, Outreachy,
... Mentors" <ffmpeg-mentors@ffmpeg.org>
Subject: [FFmpeg-devel] GSoC 2023
Date: Thu, 15 Dec 2022 15:42:23 +0100
Message-ID: <1db2257b-76a7-4065-04df-ef171210580a@mail.de> (raw)
Hi,
as we figured during the last dev meeting on December 2nd we want to apply again for GSoC 2023.
I told mentors often enough already that it's a vital point in our applications to have a properly filled results page from the last GSoC we did.
Last time no mentor cared about this - we can be quite sure that our application will fail if we don't have [1] up-to-date until we send our application.
Also vital for the application are already existing project ideas so everyone interested in mentoring a project in 2023, please add your idea(s) to [2].
The application deadline is January 23rd, I will aim for sending an application mid January.
Thanks,
Thilo
[1] https://trac.ffmpeg.org/wiki/SponsoringPrograms/GSoC/2022/Results
[2] https://trac.ffmpeg.org/wiki/SponsoringPrograms/GSoC/2023
_______________________________________________
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 reply other threads:[~2022-12-15 14:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 14:42 Thilo Borgmann [this message]
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
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=1db2257b-76a7-4065-04df-ef171210580a@mail.de \
--to=thilo.borgmann@mail.de \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=ffmpeg-mentors@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