git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Shubham Mishra <shivam828787@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Taylor Blau <me@ttaylorr.com>,
	Plato Kiorpelidis <kioplato@gmail.com>, git <git@vger.kernel.org>,
	Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
	Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [GSoC] Contributor candidate introduction
Date: Wed, 6 Apr 2022 19:41:35 +0530	[thread overview]
Message-ID: <CAC316V6mDowYpptox3KxYycpwpiQhW+LSmNOx8_F_8LKBG2gUw@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD1Y+4XDARoK_T_c2eMUou4senhQLnjJE4zyz2KHuZGsFw@mail.gmail.com>

Hi,

As the topic begans, I think I should also give my updates. Last week
I spend time around "Croaring" library and right now, I start working
on the initial version of proposal which I am planning to share by end
of this week. I think if it's possible to split it into two, We can
look forward to it with I am okay with picking other project involving
bitmap too but only issue, I have to start again from scratch :)

Thanks,
Shubham

On Wed, Apr 6, 2022 at 11:55 AM Christian Couder
<christian.couder@gmail.com> wrote:
>
> Hi Taylor, Plato and all,
>
> On Tue, Apr 5, 2022 at 11:59 PM Taylor Blau <me@ttaylorr.com> wrote:
> >
> > 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.
>
> Though we appreciate it, we don't require introducing yourself. And if
> you choose to do it, you can do it whenever you want.
>
> > 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.
>
> Unfortunately, GSoC rules forbid contributors from working 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 think this would require creating different independent project ideas.
>
> > > 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?
>
> Unfortunately, I think there needs to be a different project for each
> GSoC contributor and GSoC rules ask for each contributor to work
> independently from other GSoC contributors. It's possible to have the
> same mentors for different projects though, so if the mentors for a
> project are OK with splitting it into different independent projects
> and mentoring all the independent projects, I think it could work.
>
> Best,
> Christian.

  reply	other threads:[~2022-04-06 16:49 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
2022-04-06  6:25   ` Christian Couder
2022-04-06 14:11     ` Shubham Mishra [this message]
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

  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=CAC316V6mDowYpptox3KxYycpwpiQhW+LSmNOx8_F_8LKBG2gUw@mail.gmail.com \
    --to=shivam828787@gmail.com \
    --cc=chriscool@tuxfamily.org \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=kioplato@gmail.com \
    --cc=me@ttaylorr.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).