From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: Christian Couder <christian.couder@gmail.com>,
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, 08 Apr 2022 13:46:05 -0700 [thread overview]
Message-ID: <xmqqk0bzl2wi.fsf@gitster.g> (raw)
In-Reply-To: <YlCcQw6FuWufLe74@nand.local> (Taylor Blau's message of "Fri, 8 Apr 2022 16:34:11 -0400")
Taylor Blau <me@ttaylorr.com> writes:
> 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.
Yeah, also I doubt that bitmap stakeholders want to assign such a
centrally important design task to an apprentice, even with a
competent mentor or two.
> The "append-only" project is interesting, but probably not large enough
> for a GSoC student to occupy their time with completely.
I have to preface this with the fact I always am the one that is the
least optimistic about the timeline, but "append-only" somehow
sounds like a project with an interesting enough size and complexity
to me.
Just my two cents.
(me goes back to preparation of -rc1)
next prev parent reply other threads:[~2022-04-08 20:46 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
2022-04-08 20:46 ` Junio C Hamano [this message]
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=xmqqk0bzl2wi.fsf@gitster.g \
--to=gitster@pobox.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 \
--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.
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).