From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Christian Couder <christian.couder@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Git in GSoC 2025
Date: Sun, 19 Jan 2025 15:43:29 +0530 [thread overview]
Message-ID: <8c8e8797-8de9-4684-94a0-f6c17a592dc5@gmail.com> (raw)
Hello everyone,
It is that time of year. GSoC Org Applications for 2025 are open now[1].
They are due before Tuesday, February 11 at 1800 UTC. It's good to see
that few contributors have already started working on microprojects this
year :-)
I could help as an Org Admin like previous years. I prefer not to
volunteer as a mentor this time owing to other commitments, though.
There are no noticeable changes to the program this year.
The GSoC contributor application period is March 24 - April 8, so
(co-)mentors and org admins are already welcome to volunteer. As usual,
we also need project ideas to refresh our idea page from last year
(https://git.github.io/SoC-2024-Ideas/). Feel free to share your
thoughts and discuss. It would be great if we could come up with a good
mix of small, medium and large projects.
Do feel free to ask if there's anything that needs to be clarified.
Just like previous year, there will be a GSoC Meetup in Brussels during
FOSDEM weekend on Saturday, February 1st in the evening. If you are
around, interested and haven't received the link to register directly
from Google, let me know so I can send it to you.
[1]:
https://opensource.googleblog.com/2025/01/google-summer-of-code-2025-is-here.html
--
Sivaraam
next reply other threads:[~2025-01-19 10:13 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-19 10:13 Kaartic Sivaraam [this message]
2025-01-20 7:07 ` Git in GSoC 2025 Patrick Steinhardt
2025-01-20 13:38 ` shejialuo
2025-01-21 11:47 ` Oswald Buddenhagen
[not found] ` <CA+ARAtqfXo75PzzB3cQjDbvLxwytUK=xJiGG=VHZ1sNCcfyktQ@mail.gmail.com>
2025-01-27 8:06 ` Patrick Steinhardt
2025-01-27 12:43 ` shejialuo
2025-01-28 18:20 ` Kaartic Sivaraam
2025-01-28 17:30 ` Kaartic Sivaraam
2025-02-02 11:52 ` Kaartic Sivaraam
2025-02-03 8:45 ` Patrick Steinhardt
2025-02-03 11:53 ` Karthik Nayak
2025-02-04 2:29 ` shejialuo
2025-02-04 18:33 ` Kaartic Sivaraam
2025-02-05 13:20 ` Christian Couder
2025-02-07 7:32 ` Kaartic Sivaraam
2025-02-07 8:07 ` Christian Couder
2025-02-07 10:55 ` Patrick Steinhardt
2025-02-11 5:18 ` Kaartic Sivaraam
2025-02-16 12:56 ` Ghanshyam Thakkar
2025-02-16 13:53 ` Kaartic Sivaraam
2025-02-16 17:48 ` Junio C Hamano
2025-02-17 15:21 ` Ghanshyam Thakkar
2025-03-07 10:01 ` Karthik Nayak
2025-03-20 17:50 ` Kaartic Sivaraam
2025-03-21 21:02 ` Karthik Nayak
2025-02-08 15:34 ` shejialuo
2025-02-10 17:00 ` Karthik Nayak
2025-01-20 8:19 ` Christian Couder
2025-01-20 11:09 ` Patrick Steinhardt
2025-01-21 20:35 ` Junio C Hamano
2025-01-30 5:44 ` Kaartic Sivaraam
2025-01-30 7:32 ` Patrick Steinhardt
2025-01-30 8:37 ` Christian Couder
2025-01-30 10:56 ` Patrick Steinhardt
2025-01-30 19:18 ` Junio C Hamano
2025-01-30 21:00 ` Junio C Hamano
2025-01-31 4:51 ` Patrick Steinhardt
2025-01-31 16:09 ` Junio C Hamano
2025-02-03 8:49 ` Patrick Steinhardt
2025-01-31 4:48 ` Patrick Steinhardt
2025-02-03 13:21 ` Junio C Hamano
2025-02-04 18:36 ` Kaartic Sivaraam
2025-01-30 5:39 ` Kaartic Sivaraam
2025-01-20 10:12 ` Karthik Nayak
2025-01-20 13:27 ` shejialuo
2025-02-28 3:03 ` Kaartic Sivaraam
2025-02-28 5:06 ` shejialuo
2025-02-28 6:16 ` Patrick Steinhardt
2025-02-28 7:56 ` Christian Couder
2025-02-28 10:12 ` Ghanshyam Thakkar
2025-03-01 0:47 ` Kaartic Sivaraam
2025-03-03 10:00 ` Karthik Nayak
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=8c8e8797-8de9-4684-94a0-f6c17a592dc5@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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
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;
as well as URLs for NNTP newsgroup(s).