From: Raja Rathour via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: Michael Niedermayer <michael@niedermayer.cc>
Cc: FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>, "Guo, Yejun" <yejun.guo@intel.com>,
Raja Rathour <imraja729@gmail.com>
Subject: [FFmpeg-devel] Re: [GSoC][RFC] GSoC 2026 Proposal (350 Hours): High-Performance LibTorch Backend Modernization
Date: Mon, 26 Jan 2026 16:16:43 +0530
Message-ID: <CAMo0W6PJEDGmGLe09Z0=gphhmWFttAz2etV+BaLo0A7Rs7+=Nw@mail.gmail.com> (raw)
In-Reply-To: <aXbZcnxImmLE6K6L@neo>
>
> Hi Michael,
>
> Thank you for the positive feedback and for supporting the effort to
> modernize the LibTorch backend. I'm glad to hear you see the value in this
> project.
>
> I would be happy to add this to the GSoC 2026 ideas page immediately to
> ensure the organization's project list is well-represented for Google's
> review. However, I am encountering a "404 Not Found" error whenever I
> attempt to register an account at
> https://trac.ffmpeg.org/wiki/SponsoringPrograms/GSoC/2026
>
> Could you please advise if there is a specific procedure for obtaining a
> Trac account, or should I provide the Wiki-formatted text here for a
> maintainer to post on my behalf?
>
> Best regards,
>
> Raja Rathour
>
_______________________________________________
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-26 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 17:00 [FFmpeg-devel] " Raja Rathour via ffmpeg-devel
2026-01-26 3:03 ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2026-01-26 10:46 ` Raja Rathour via ffmpeg-devel [this message]
2026-01-26 23:58 ` Michael Niedermayer 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='CAMo0W6PJEDGmGLe09Z0=gphhmWFttAz2etV+BaLo0A7Rs7+=Nw@mail.gmail.com' \
--to=ffmpeg-devel@ffmpeg.org \
--cc=imraja729@gmail.com \
--cc=michael@niedermayer.cc \
--cc=yejun.guo@intel.com \
/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