From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] Too many project ideas in GSOC 2022 FFmpeg
Date: Mon, 21 Feb 2022 13:12:29 +0100
Message-ID: <20220221121229.GY2829255@pb2> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 561 bytes --]
Hi all
We have 0 project ideas on our gsoc 2022 page
well we have 2 now as i copied my two from last year
If you have an idea, please add it!
If you had one in 2021 or prior which was not finished and the project
still makes sense, please copy it to the 2022 page
https://trac.ffmpeg.org/wiki/SponsoringPrograms/GSoC/2022
google doesnt like empty idea pages when they review it!
Thanks!
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Never trust a computer, one day, it may think you are the virus. -- Compn
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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-02-21 12:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 12:12 Michael Niedermayer [this message]
2022-02-21 16:59 ` Pierre-Anthony Lemieux
2022-02-21 18:24 ` Michael Niedermayer
2022-02-23 16:22 ` Michael Niedermayer
2022-02-23 17:07 ` Mark Gaiser
2022-03-01 7:46 ` Michael Koch
2022-03-01 8:09 ` Paul B Mahol
2022-03-01 17:49 ` Marvin Scholz
2022-03-02 11:46 ` Paul B Mahol
2022-03-01 15:17 ` Michael Niedermayer
2022-03-03 19:47 ` Paul B Mahol
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=20220221121229.GY2829255@pb2 \
--to=michael@niedermayer.cc \
--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