git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Git Community <git@vger.kernel.org>
Cc: 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>,
	ZheNing Hu <adlternative@gmail.com>
Subject: Git in GSoC 2022?
Date: Wed, 26 Jan 2022 23:59:16 +0530	[thread overview]
Message-ID: <439ebfba-d493-2cff-434a-b1073e755688@gmail.com> (raw)

Hi all,

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?


Also, wanted to note that GSoC has some changes in store for
this year [5]. Concisely they are:

   - Expanding eligibility: the program is now open to non-students.

   - Multiple Sizes of Projects: In 2021, project size was reduced
     (~175 hours). This year, both medium sized projects (~175 hours)
     and large projects (~350 hours) are supported.

     GSoC organizers recommend communities to have both medium _and_
     large size projects.

   - Increased timing flexibility: rather than a mandatory 12-week
     program, projects can be extended for up to 22 weeks by the
     mentor and the contributors.

See the blog [5] for more details.


[ References ]

[1]: https://developers.google.com/open-source/gsoc/timeline

[2]: https://git.github.io/Outreachy-23-Microprojects/

[3]: https://git.github.io/SoC-2021-Ideas/

[4]: https://public-inbox.org/git/YVTM+WQH%2FUyhVeTz@nand.local/

[5]: https://opensource.googleblog.com/2021/11/expanding-google-summer-of-code-in-2022.html

-- 
Sivaraam

             reply	other threads:[~2022-01-26 18:29 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 18:29 Kaartic Sivaraam [this message]
2022-01-26 20:05 ` Git in GSoC 2022? 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
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

  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=439ebfba-d493-2cff-434a-b1073e755688@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.
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).