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 Org Apps - review yours ASAP for common issues
Date: Sun, 11 Feb 2024 20:22:23 +0100
Message-ID: <20240211192223.GT6401@pb2> (raw)


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

Hi all

just got this today, and to avoid anyone being upset of not knowing
about something again.

I dont know if this applies to us but posting it here
Also iam not doing gsoc admin (iam just really the last resort backup
i dont have time for gsoc) but it seemes
someone fillled everything out already i saw some "100%"
in the brief moments between "Something went wrong." and "400 errors"

thx

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

Date: Sun, 11 Feb 2024 10:36:02 -0800
From: summerofcode-noreply@google.com
To: michael@niedermayer.cc
Subject: GSoC Org Apps - review yours ASAP for common issues

Google Summer of Code


We are sending this email to all Org Admins of Orgs that applied to GSoC 2024.

This year we have noticed a large number of org apps are missing required information or having issues with project sizes. Please review your org app for these common mistakes that could result in your org app being rejected.


Project sizes need to be scoped to 90, 175 or 350 hours (you can not have a project that is 200 hours, or some other random number of hours).
Make sure your Project Ideas list is public so GSoC Google reviewers can access it.
Make sure your Project Ideas include the ALL of the required information below:

a) a project title/description b) more detailed description of the project (2-5 sentences) c) expected outcomes d) skills required/preferred e) possible mentors f) expected size of project (90, 175 or 350 hour – yes, 3 options starting in 2024). And if possible, an easy, intermediate or hard/difficult rating of each project. This helps the more inexperienced folks not get overwhelmed and they can focus on reviewing easy project ideas.

You should already have your ideas list mostly complete. While it is okay to continue to add Project Ideas you should not have an empty project ideas list as Google Admins are reviewing these applications (and have been for the last 5+ days) and we need to see ideas posted to be able to consider your application.

Thanks, we look forward to sending out the notifications of project acceptance Tuesday, February 20th. This is 1 day before we announce the accepted orgs publicly to give orgs a chance to organize their mentors before the GSoC contributors start actively reaching out to orgs.

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.

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

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

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

He who knows, does not speak. He who speaks, does not know. -- Lao Tsu

[-- 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-02-11 19:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240211192223.GT6401@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