From: Yury German <Blueknight@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Google Summer of Code for Gentoo for the year 2025
Date: Tue, 14 Jan 2025 15:26:47 -0500 [thread overview]
Message-ID: <715F381B-7EA6-4651-AA96-10AFB00F140E@gentoo.org> (raw)
Hey everyone!
The Google Summer of Code (GSoC) has announced the new application deadline for organizations. Gentoo needs to submit their application with proposed projects by February 11th. They’ve specifically requested more “Security and AI/ML” projects for GSoC.
We’re seeking volunteers to assist as Mentors or Co-Mentors for this year’s summer of code. As part of this initiative, we’re eager to come up with fresh ideas to replace (or ideally, all) of the projects from last year’s summer of code. You can find the ideas page for the 2024 Gentoo GSoC page.
If you’re willing to volunteer as a mentor, please let me know via email or in IRC. There’s also an IRC channel set up for discussions related to SOC information (#gentoo-soc).
We are thrilled to welcome developers who are eager to contribute!
Thanks,
BlueKnight
next reply other threads:[~2025-01-14 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 20:26 Yury German [this message]
2025-01-24 20:23 ` [gentoo-dev] Google Summer of Code for Gentoo for the year 2025 Andrey F.
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=715F381B-7EA6-4651-AA96-10AFB00F140E@gentoo.org \
--to=blueknight@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox