From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Nuo Mi <nuomi2021@gmail.com>, Lynne <dev@lynne.ee>,
Niklas Haas <ffmpeg@haasn.xyz>
Subject: [FFmpeg-devel] GSoC 2025 [For mentors]
Date: Mon, 24 Mar 2025 11:41:49 +0100
Message-ID: <20250324104149.GP4991@pb2> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1270 bytes --]
Hi all
3 Mentors have not agreed to the google contracts for 2025
To add Mentors to FFmpeg GSoC 2025, the process seems to be now:
1. Admin needs to invite each mentor to the "year independant list" (this is done)
2. Each mentor needs to agree to 2 google documents on the webpage for 2025
3. Admins need to add each member to the 2025 list of mentors after 2.
3 mentors (in CC) have not done "2.", Admins cannot invite them as they
already are invited and have already joined (last year or before)
Iam not 100% sure where to agree to these 2025 documents
but for me they are here: https://summerofcode.withgoogle.com/profile
Thats the text google provided for this:
"All Org Admins should be adding Mentors now. Remember, you are about to get swarmed with interested contributors reaching out to you next week (a lot more than these past couple of weeks) so add your Mentors to the 2025 program now. Yes, you have to add people again this year even if they participated last year as they must agree to the 2025 Program Rules to be a 2025 Mentor or Org Admin."
thx
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The greatest way to live with honor in this world is to be what we pretend
to be. -- Socrates
[-- 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-03-24 10:42 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=20250324104149.GP4991@pb2 \
--to=michael@niedermayer.cc \
--cc=dev@lynne.ee \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=ffmpeg@haasn.xyz \
--cc=nuomi2021@gmail.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