All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Plato Kiorpelidis <kioplato@gmail.com>
Cc: git@vger.kernel.org, shivam828787@gmail.com,
	kaartic.sivaraam@gmail.com,
	Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [GSoC] Contributor candidate introduction
Date: Tue, 5 Apr 2022 17:59:33 -0400	[thread overview]
Message-ID: <Yky7xb7nQRR8Vqtj@nand.local> (raw)
In-Reply-To: <CAO2gv81zCGbxNN_7a2j7sJZ_fbHiFXf4YxagddWLBWw7-ki5zw@mail.gmail.com>

Hi Plato,

On Wed, Apr 06, 2022 at 12:43:59AM +0300, Plato Kiorpelidis wrote:
> Hello,
>
> I'm interested in participating as contributor for the project
> "Reachability bitmap improvements".
> The area I'm interested in, the most, is the alternate compression scheme
> e.g. Roaring+Run, however I'm ecstatic about any bitmap performance improvement.
> Expected project size I'm targeting for is large (350 hours).
> I've already completed my micro-project and I will submit it in a few hours.
> I wanted to be sure I could submit v1 of it before committing to
> introducing myself.

Hooray! I'm delighted to hear that you're interested.

> I've gone through the mailing list and looked for other candidates that could
> also be interested in this project. Shubham Mishra is also interested.
> - Could we collaborate on this project considering how broad it is or only one
> can be selected?
> He/she already has experience in open source and has participated in
> GSoC before.

I think there are a couple of options here, since we have a handful of
bitmap-related projects that are all up for grabs. If Shubham is also
interested in working on implementing Roaring+Run compression, then I
would be happy for the two of you to work together.

Alternatively, if you each want to focus on different sub-projects, I
would be happy to work with multiple students on different areas within
the reachability bitmaps subsystem.

> I should note that the best case scenario for me is if we are both selected,
> probably on different bitmap performance areas under "Reachability bitmap
> improvements" project, however I don't know if it's possible. It probably
> depends on the mentors listed for this project and the work load involved.

Yeah. Even though I'd be happy to work with as many students as I have
time for, I'm not sure whether it's possible within GSoC's own rules,
much less whether or not it's been done before.

Christian (cc'd) may have more information. Christian: is it possible to
accept multiple students for the same GSoC project?

Thanks,
Taylor

  reply	other threads:[~2022-04-06  5:07 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05 21:43 [GSoC] Contributor candidate introduction Plato Kiorpelidis
2022-04-05 21:59 ` Taylor Blau [this message]
2022-04-06  6:25   ` Christian Couder
2022-04-06 14:11     ` Shubham Mishra
2022-04-06 15:40       ` Taylor Blau
2022-04-06 15:43     ` Taylor Blau
2022-04-06 20:11       ` Kaartic Sivaraam
2022-04-07  7:16         ` Christian Couder
2022-04-07  9:25           ` Abhradeep Chakraborty
2022-04-08 20:34           ` Taylor Blau
2022-04-08 20:46             ` Junio C Hamano
2022-04-13 20:55             ` Taylor Blau
2022-04-15 21:01               ` Plato Kiorpelidis
2022-04-18 17:54 ` Kaartic Sivaraam
2022-04-18 18:06   ` Abhradeep Chakraborty
2022-04-19  4:38     ` Shubham Mishra
2022-04-19 15:54     ` Abhradeep Chakraborty
2022-04-18 18:24   ` Kaartic Sivaraam
2022-04-19 13:16     ` Jayati Shrivastava
2022-04-19 17:40       ` Kaartic Sivaraam
2022-04-20 13:16         ` Labnan Khalid Masum
2022-04-20 19:40           ` Kaartic Sivaraam
2022-04-21  8:58           ` Christian Couder
2022-04-18 18:33   ` Plato Kiorpelidis
2022-05-09  6:44   ` Kaartic Sivaraam
2022-05-09 15:12     ` Shubham Mishra
2022-05-09 16:36       ` Taylor Blau
2022-05-09 20:13     ` Plato Kiorpelidis
  -- strict thread matches above, loose matches on Subject: below --
2022-04-05 21:30 Plato Kiorpelidis

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=Yky7xb7nQRR8Vqtj@nand.local \
    --to=me@ttaylorr.com \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=kioplato@gmail.com \
    --cc=shivam828787@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.