git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: git <git@vger.kernel.org>, Taylor Blau <me@ttaylorr.com>,
	 Junio C Hamano <gitster@pobox.com>,
	Victoria Dye <vdye@github.com>, Patrick Steinhardt <ps@pks.im>
Subject: Re: Git in GSoC 2024
Date: Tue, 30 Jan 2024 09:38:48 +0100	[thread overview]
Message-ID: <CAP8UFD1VAvnkM6afZvtpdXhA4csDBDwMnF9yUzSx_ut-Ypf+eA@mail.gmail.com> (raw)
In-Reply-To: <1de82b27-116a-450e-98c0-52eb65a8f608@gmail.com>

Hi Kaartic and all,

On Mon, Jan 29, 2024 at 7:16 PM Kaartic Sivaraam
<kaartic.sivaraam@gmail.com> wrote:
>
> 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.

Thanks a lot for sending this and for volunteering as an Org Admin and
possibly as a mentor too!

> 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."

Unless some mentors are only willing to mentor Small projects, I don't
think it's a good idea to propose such projects. Except for some very
good contributors, I think it usually takes a long time for the
contributors we mentor to become efficient and autonomous enough by
themselves. So I think a Small project would likely leave the
contributor halfway there, and they would then have trouble continuing
to work on their project if it's not finished or contributing
significantly in some way afterwards.

> 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.

I am volunteering as both an Org Admin and a mentor too.

I am not sure how many tests there are left to be ported to the new
unit test framework. Patrick told me about porting some reftable unit
tests to the new unit test framework though. So it might still work as
a GSoC project.

> 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.

Unfortunately I cannot attend the FOSDEM this year. Thanks for
mentioning this though! It's a great opportunity to meet GSoC people
and open source people in general.


  reply	other threads:[~2024-01-30  8:39 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 18:16 Git in GSoC 2024 Kaartic Sivaraam
2024-01-30  8:38 ` Christian Couder [this message]
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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAP8UFD1VAvnkM6afZvtpdXhA4csDBDwMnF9yUzSx_ut-Ypf+eA@mail.gmail.com \
    --to=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=me@ttaylorr.com \
    --cc=ps@pks.im \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).