From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Noah Johannessen <njohannessen@tamu.edu>,
Kieran Kunhya <kieran618@googlemail.com>
Subject: [FFmpeg-devel] Re: Quick question from a CS student at TAMU
Date: Sat, 24 Jan 2026 16:42:06 +0000
Message-ID: <CABGuwEnobc65n1HE5TM39cQo5hnNcMeqkS0NPLPWa9qptWUkKQ@mail.gmail.com> (raw)
In-Reply-To: <CAAKa-rzxw_2o61=e66MPS-5U=zUQ5qJFK-wAA82j_wfv9KfAjQ@mail.gmail.com>
On Sat, 24 Jan 2026, 15:58 Noah Johannessen via ffmpeg-devel, <
ffmpeg-devel@ffmpeg.org> wrote:
> Howdy!
>
> I hope you don’t mind the cold outreach. I’m a CS student at Texas A&M
> who’s been following some of the work coming out of the GSoC ecosystem, and
> your involvement caught my eye.
>
> I’m exploring a small, student-led project this spring. As part of that,
> I’ve been reaching out to a few folks whose judgment I respect to get a
> sense for what kinds of problems are actually useful to work on.
>
> In particular, I was curious whether you’d ever be open to students taking
> on a well scoped project aligned with your work. Even a quick gut check on
> whether that’s something you ever consider would be super helpful.
>
> I appreciate the work you’ve done in the space!
>
> Best,
>
> Noah Johannessen
> Texas A&M University Computer Science
> (281) 908-3152
>
Yes but if I recall correctly the Gsoc project must be solely for Gsoc and
not for any other student projects, employment etc.
>
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2026-01-24 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e860881014.9a9@mailsuite.com>
2026-01-22 21:30 ` [FFmpeg-devel] " Noah Johannessen via ffmpeg-devel
2026-01-24 16:42 ` Kieran Kunhya via ffmpeg-devel [this message]
2026-01-24 16:43 ` [FFmpeg-devel] " ff--- via ffmpeg-devel
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=CABGuwEnobc65n1HE5TM39cQo5hnNcMeqkS0NPLPWa9qptWUkKQ@mail.gmail.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=kieran618@googlemail.com \
--cc=njohannessen@tamu.edu \
/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