Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] Fw: GSoC 2025: Please review your Project Ideas lists
Date: Fri, 14 Feb 2025 20:28:34 +0100
Message-ID: <20250214192834.GX1904408@pb2> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1810 bytes --]

Hi everyone

Please help improve the gsoc 2025 page

2 ideas are missing backup mentors, if you are able please
add yourself to them as backup mentor

Also please add more ideas!
And help review the page and ideas to ensure it is all in good shape.

thx

----- Forwarded message from summerofcode-noreply@google.com -----

Date: Thu, 13 Feb 2025 20:38:55 -0800
From: summerofcode-noreply@google.com
To: michael@niedermayer.cc
Subject: GSoC 2025: Please review your Project Ideas lists

Google Summer of Code


Hello,

We are carefully reviewing the 2025 GSoC Org applications and are discovering an alarming number of orgs with only a couple of ideas or ideas that haven't been updated since 2023 or 2024. Please make sure your project ideas are all in your lists NOW, we can only review what is there and if you have an incomplete list you risk your org being rejected this year.

We have more people on our review team than ever before and are taking a very close look at all applications this year, including individual ideas and discovering quite a few that are way overscoped for GSoC and even a few that are inappropriate ideas for the program. Please review your lists, Org Admins it is your responsibility to be sure the Project Ideas represent your org appropriately.

Best,

Stephanie Taylor

GSoC Program Lead




https://summerofcode.withgoogle.com

For any questions, please contact gsoc-support@google.com. Replies to this message go to an unmonitored mailbox.

© 2025 Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA







----- End forwarded message -----

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

In a rich man's house there is no place to spit but his face.
-- Diogenes of Sinope

[-- 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".

             reply	other threads:[~2025-02-14 19:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-14 19:28 Michael Niedermayer [this message]
2025-02-14 20:20 ` Kieran Kunhya via ffmpeg-devel
2025-02-14 20:30   ` Michael Niedermayer
2025-02-14 21:29   ` Steven Liu
2025-02-14 22:14     ` Kieran Kunhya via ffmpeg-devel
2025-02-14 23:30       ` Steven Liu
2025-02-15 15:06         ` Michael Niedermayer
2025-02-15 15:14         ` Michael Niedermayer
2025-02-15 15:41           ` Steven Liu

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=20250214192834.GX1904408@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