All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: ZheNing Hu <adlternative@gmail.com>
Cc: Git Community <git@vger.kernel.org>,
	Christian Couder <christian.couder@gmail.com>,
	Junio C Hamano <gitster@pobox.com>, Taylor Blau <me@ttaylorr.com>,
	Emily Shaffer <emilyshaffer@google.com>,
	Atharva Raykar <raykar.ath@gmail.com>
Subject: Re: Git in GSoC 2022?
Date: Sat, 29 Jan 2022 23:13:20 +0530	[thread overview]
Message-ID: <d7000284-0964-e929-681f-a902b2b3b917@gmail.com> (raw)
In-Reply-To: <CAOLTT8QzaM70_jk4bOnBAHFaNjf6d_WSNp4h-qLWr2eJLdErBg@mail.gmail.com>

On 27/01/22 8:30 pm, ZheNing Hu wrote:
> Kaartic Sivaraam <kaartic.sivaraam@gmail.com> 于2022年1月27日周四 02:29写道:
>>
>> GSoC 2022 is approaching. The timeline has been released [1].
>> Mentoring organizations should submit applications between
>> February 7 and 21 at 1800 UTC. So, I thought I'll kick off
>> the discussion about our plans for GSoC 2022.
>>
>> First, are we interested in participating in the 2022 round of
>> GSoC?
>>
>> If we are interested in participating we need:
>>
>>     - Volunteers who are wiling to act as mentors. I would be
>>       willing to be volunteer myself as a mentor for one student.
>>
>>     - Microprojects: I believe we could repurpose the Outreachy
>>       microproject ideas[2] for GSoC too. If others have suggestions
>>       for microproject ideas, please share them.
>>
>>     - Project ideas: There are two mentioned in SoC-2021-Ideas[3]
>>       but both were picked by GSoC students the previous year. So,
>>       we would need new ones this year.
>>
>>       Taylor showed interest in a bitmap-related project during
>>       the Outreachy application period [4]. Taylor, are you still
>>       interested in mentoring a bitmap-related project? Would it
>>       be possible for you to do so for the upcoming GSoC?
>>
>>
> 
> I've been busy preparing for some internships lately and may not have
> enough time as a mentor to help this year's GSOC students, but I can
> occasionally provide my review for interesting projects this year.
> 

No worries. Reviews would be great when you're able to find time for them.
Thanks! :-)

-- 
Sivaraam

  reply	other threads:[~2022-01-29 17:43 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 18:29 Git in GSoC 2022? Kaartic Sivaraam
2022-01-26 20:05 ` Taylor Blau
2022-01-27  9:32   ` Christian Couder
2022-01-29 18:09     ` Kaartic Sivaraam
2022-02-13 13:35     ` Christian Couder
2022-02-15 20:34       ` Kaartic Sivaraam
2022-02-15 23:18       ` Hariom verma
2022-02-16 15:40         ` Christian Couder
2022-02-17 15:07           ` Hariom verma
2022-02-17 17:18           ` Kaartic Sivaraam
2022-02-18  2:14             ` Hariom verma
2022-02-26 20:29   ` Kaartic Sivaraam
2022-02-28 11:03     ` Christian Couder
2022-02-28 18:02       ` Kaartic Sivaraam
2022-03-01 13:51         ` Christian Couder
2022-03-04 18:34           ` Kaartic Sivaraam
2022-01-27  3:55 ` Bagas Sanjaya
2022-01-27  9:44   ` Christian Couder
     [not found]     ` <nycvar.QRO.7.76.6.2201281114440.347@tvgsbejvaqbjf.bet>
2022-01-29 18:36       ` Kaartic Sivaraam
2022-03-09 11:49         ` Johannes Schindelin
2022-03-09 19:57           ` Kaartic Sivaraam
2022-01-27 14:39 ` Derrick Stolee
2022-01-29 18:19   ` Kaartic Sivaraam
2022-02-02 17:42     ` Derrick Stolee
2022-01-27 15:00 ` ZheNing Hu
2022-01-29 17:43   ` Kaartic Sivaraam [this message]
2022-02-03 14:12 ` Philip Oakley
2022-02-12 18:12   ` Kaartic Sivaraam
2022-02-13  9:33     ` Christian Couder
2022-02-15 15:05       ` Philip Oakley
2022-02-15 20:32       ` Kaartic Sivaraam
2022-02-16 15:55         ` Christian Couder
2022-02-17 17:28           ` Kaartic Sivaraam
2022-03-07 19:38 ` Kaartic Sivaraam
2022-03-07 19:50   ` Derrick Stolee
2022-03-07 22:25   ` Hariom verma

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=d7000284-0964-e929-681f-a902b2b3b917@gmail.com \
    --to=kaartic.sivaraam@gmail.com \
    --cc=adlternative@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=me@ttaylorr.com \
    --cc=raykar.ath@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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.