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>
Cc: Thilo Borgmann <thilo.borgmann@mail.de>,
	"Reynaldo H. Verdejo Pinochet" <rverdejo@gmail.com>
Subject: [FFmpeg-devel] Fw: Your GSoC Org has 0 Contributors ranked - deadline is 1800 UTC April 24
Date: Wed, 24 Apr 2024 01:50:31 +0200
Message-ID: <20240423235031.GC2318149@pb2> (raw)


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

Hi all

I just got the mail below. I assume the other admins are going to rank them
before the deadline like they did last year. (but i can of course not assume
that because there is no time if that doesnt happen)
I have not followed GSoC last year or this year much ...

Either way, if you are a mentor and want your student to receive a slot
tell me privatly (with thilo and reynaldo in CC) ASAP how you would
rank your student. And i will rank him/her accordingly if i see noone
else starting to assign ranks

thx

----- Forwarded message from Stephanie Taylor <sttaylor@google.com> -----

Date: Tue, 23 Apr 2024 15:55:36 -0700
From: Stephanie Taylor <sttaylor@google.com>
To: undisclosed-recipients: ;
Subject: Your GSoC Org has 0 Contributors ranked - deadline is 1800 UTC April 24

Hello GSoC Org Admin,


You are receiving this email because you are an Org Admin and your org
currently has 0 (zero) GSoC 2024 proposals ranked and thus have not
requested any GSoC contributors.

If your org would like to accept GSoC contributors this year, an Org Admin
must rank proposals before tomorrow, Wednesday April 24 at 1800 UTC.

Org Admins should verify they have Ranked all the proposals their Org
wishes to select for GSoC 2024 before the deadline this Wednesday, April 24
at 18:00 UTC. You must have proposals ranked with at least one assigned
mentor in order for Google Admins to consider your request. If your org
does not rank your requested proposals and assign mentors we will not be
able to grant you any GSoC 2024 contributors.

As of right now (2238 UTC), you have less than 20 hours to complete this
task. Please refer back to the email we sent you on Sunday, April 21st for
further instructions on this task or read that email in the GSoC 2024
Mentor and Org Admin email archive.
Not planning to accept any GSoC Contributors this year?

If your org does not plan to accept any GSoC Contributors for GSoC 2024
that is fine, please send a quick email to gsoc-support@google.com saying
as much so we know this was your intention and we won’t email you to ask
what happened.

Please contact us at gsoc-support@google.com with any questions.

Best,

Stephanie



Stephanie Taylor  |  Program Manager

Celebrating *20 years* of

*Google Summer of Code* in 2024!

g.co/gsoc  <http://g.co/gsoc>

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

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

When the tyrant has disposed of foreign enemies by conquest or treaty, and
there is nothing more to fear from them, then he is always stirring up
some war or other, in order that the people may require a leader. -- Plato

[-- 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:[~2024-04-23 23:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 23:50 Michael Niedermayer [this message]
2024-04-23 23:56 ` Michael Niedermayer
2024-04-24  5:59   ` Thilo Borgmann via ffmpeg-devel
2024-04-24  7:57     ` Michael Niedermayer

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=20240423235031.GC2318149@pb2 \
    --to=michael@niedermayer.cc \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=rverdejo@gmail.com \
    --cc=thilo.borgmann@mail.de \
    /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