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@xxxxxxxxx> wrote: > > Hi Taylor, Plato and all, > > On Tue, Apr 5, 2022 at 11:59 PM Taylor Blau <me@xxxxxxxxxxxx> 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.
