From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: git <git@vger.kernel.org>
Cc: Christian Couder <christian.couder@gmail.com>,
Taylor Blau <me@ttaylorr.com>, Junio C Hamano <gitster@pobox.com>,
Victoria Dye <vdye@github.com>
Subject: Git in GSoC 2024
Date: Mon, 29 Jan 2024 23:46:26 +0530 [thread overview]
Message-ID: <1de82b27-116a-450e-98c0-52eb65a8f608@gmail.com> (raw)
Hi everyone,
GSoC Org Applications for 2024 are open now [1] and are due before
Tuesday, February 6 at 1800 UTC. It's good to see that contributors have
already started working on microprojects this year :-)
I could help as an Org Admin like previous years. I could volunteer as a
mentor depending on the set of available projects that we're able to
gather for this year.
There are one noticeable change to the program that should be highlighted:
"For 2024 we have the concept of Small ~90 hour projects that are a
standard 8 weeks long (they can extended but it is suggest not
extending beyond 12 weeks for the small projects). We aren't
required to have small projects available but might be worth
considering if we have any small projects that contributors could
work on."
The GSoC contributor application deadline is April 2 - 18:00 UTC, 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-2023-Ideas/). Feel free to share your
thoughts and discuss.
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 3rd 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.
There's also seems to be a GSoC stand at FOSDEM on Saturday or Sunday.
It's said to be located in building H, level 1.
[1]:
https://opensource.googleblog.com/2024/01/google-summer-of-code-2024-mentor-organization-applications-now-open.html
--
Sivaraam
next reply other threads:[~2024-01-29 18:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 18:16 Kaartic Sivaraam [this message]
2024-01-30 8:38 ` Git in GSoC 2024 Christian Couder
2024-01-30 9:08 ` Patrick Steinhardt
2024-01-31 13:10 ` Patrick Steinhardt
2024-01-31 17:57 ` Kaartic Sivaraam
2024-01-31 18:03 ` Kaartic Sivaraam
2024-02-01 9:00 ` Karthik Nayak
2024-02-01 9:38 ` Patrick Steinhardt
2024-02-03 11:41 ` Kaartic Sivaraam
2024-02-04 14:29 ` Kaartic Sivaraam
2024-02-05 8:39 ` [PATCH] Add ideas for " Patrick Steinhardt
2024-02-05 16:43 ` Christian Couder
2024-02-05 18:55 ` Kaartic Sivaraam
2024-02-06 5:51 ` Patrick Steinhardt
2024-02-06 8:13 ` Christian Couder
2024-02-08 14:02 ` Kaartic Sivaraam
2024-02-09 6:27 ` Patrick Steinhardt
2024-02-09 8:36 ` Christian Couder
2024-02-06 5:47 ` Patrick Steinhardt
2024-02-06 8:26 ` Christian Couder
2024-02-05 17:07 ` Git in " Christian Couder
2024-02-05 18:39 ` Kaartic Sivaraam
2024-02-21 5:02 ` Kaartic Sivaraam
2024-02-21 6:19 ` Patrick Steinhardt
2024-02-21 8:43 ` Christian Couder
2024-02-21 8:59 ` Karthik Nayak
2024-02-22 4:31 ` Kaartic Sivaraam
2024-02-22 7:49 ` Patrick Steinhardt
2024-02-22 8:57 ` Karthik Nayak
2024-02-22 12:02 ` Christian Couder
2024-02-22 14:05 ` Kaartic Sivaraam
2024-02-22 15:52 ` Patrick Steinhardt
2024-02-24 17:34 ` Kaartic Sivaraam
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=1de82b27-116a-450e-98c0-52eb65a8f608@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
--cc=vdye@github.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).