git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
	Plato Kiorpelidis <kioplato@gmail.com>, git <git@vger.kernel.org>,
	Shubham Mishra <shivam828787@gmail.com>,
	Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [GSoC] Contributor candidate introduction
Date: Fri, 8 Apr 2022 16:34:11 -0400	[thread overview]
Message-ID: <YlCcQw6FuWufLe74@nand.local> (raw)
In-Reply-To: <CAP8UFD1x-JEX8MAmpabK4RbKgmVm1VQYNJdX3fP8Op5WMfUgVg@mail.gmail.com>

On Thu, Apr 07, 2022 at 09:16:44AM +0200, Christian Couder wrote:
> > > That said, if we do end up splitting the bitmaps GSoC project in two,
> > > when would we need to do it by?
> >
> > To the best of my knowledge, Google does not require the proposal ideas to
> > be laid out by organization before the proposal deadline (which is April 19).
> > This gives the flexibility for mentors and GSoC contributors to collaborate
> > and come up with a project ideas that are not present in the initial ideas
> > list and write proposals for them.
>
> I agree with this, but please keep in mind that in
> https://git.github.io/General-Application-Information/ we ask
> applicants to "Discuss their project by posting drafts of their
> application on the mailing-list long before the deadline." So
> splitting the bitmap project should be done soon, so that applicants
> have time to prepare and discuss their proposals based on the splitted
> project.

I've thought a little bit more about this, and I think we should leave
the project in one piece (i.e., avoid splitting it up).

My thinking is roughly that of the sub-projects listed:

  - investigate replacing EWAH with Roaring+Run
  - add a "table of contents" to the .bitmap file
  - append-only bitmap generation
  - amorphous / larger related projects

...the first two both require serious (re-)consideration of the .bitmap
format, and I don't think it's possible to split that up among multiple
GSoC projects.

The "append-only" project is interesting, but probably not large enough
for a GSoC student to occupy their time with completely. I think the
last bullet point has the opposite problem, which is that there is _too_
much to do there, and that it isn't well defined enough.

So we _could_ split the two projects up, having one work on any
preliminary format changes, and the other stay busy with a smaller
bitmap project, but I have significant concerns about that setup being
successful.

Instead, let's keep the project as-is, and have the accepted student
focus on one of the first two bullet points, taking into account that
we'll first want to spend some time thinking about whether or not the
current .bitmap format is appropriate given the proposed changes.

Thanks,
Taylor

  parent reply	other threads:[~2022-04-08 20:34 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
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 [this message]
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=YlCcQw6FuWufLe74@nand.local \
    --to=me@ttaylorr.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=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 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 NNTP newsgroup(s).