{"thread":{"id":"57682","subject":"[GSoC][RFC][PROPOSAL] Reachability bitmap improvements","startedAt":"2022-04-06T21:18:22Z","lastAt":"2022-04-15T05:23:49Z","messageCount":5,"participants":["Abhradeep Chakraborty","Kaartic Sivaraam"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"453223","messageId":"20220406200959.27096-1-chakrabortyabhradeep79@gmail.com","threadId":"57682","inReplyTo":null,"subject":"[GSoC][RFC][PROPOSAL] Reachability bitmap improvements","fromName":"Abhradeep Chakraborty","fromEmail":"chakrabortyabhradeep79@gmail.com","sentAt":"2022-04-06T20:09:59Z","receivedAt":"2022-04-06T21:18:22Z","isPatch":false,"sender":{"key":"chakrabortyabhradeep79@gmail.com","avatar":"https://avatars.githubusercontent.com/u/75240995?v=4"},"body":"Hello everyone,\n\nHere is the initial version of my proposal on \"Reachability bitmap\nimprovements\". I would really love to have comments on it. If you\nfind any mistakes please notify me about that.\n\nThe proposal template is inspired by Hariom Verma's (This year's\nGSoC mentor) previous year's gsoc proposal.\n\nThanks :)\n\n=============================================\n\nView on Docs: https://docs.google.com/document/d/15tZ5QbMtYN41No5wdMw-2Ilp63vquB7OqAwBCLl_0n0/edit?usp=sharing\n\n==============================================\n\n**Reachability bitmap improvements**\n\nName  :  Abhradeep Chakraborty\nMajor : Information Technology\nMobile No. : [ ... ]\nEmail : chakrabortyabhradeep79@gmail.com\nGitHub Profile: (Abhra303)[https://github.com/Abhra303]\nLinkedIn : www.linkedin.com/in/abhradeep-chakraborty-b36426201\nTime Zone : Indian Standard Time ( IST ) ( UTC +05:30 )\n\n## About Me\n\nI am Abhradeep Chakraborty, currently pursuing B.Tech in Information\nTechnology (now in my 3rd year) at Jalpaiguri Government Engineering\nCollege, India.\n\nIn the last two years, I mainly concentrated on learning and building\nweb development things. I mainly use Django, React for my projects. But\nfor the past 6 months, I have been learning about devops, cloud technologies\n( e.g. docker, Kubernetes, AWS etc.), computer networking and core\ntechnologies (such as git, linux, gcc etc.). I also have an interest in\nsome research based technologies like WebRTC, Web3 etc.\n\nMy ultimate objective is to be a dedicated and active contributor to all\nof these technologies. So, I want to start this contribution journey with\n`git` and therefore I want to be a part of this GSoC program.\n\n## Me & Git\n\nI have started exploring the Git codebase since Sept 2021. At first, I\nmainly focused on knowing the git internals. During this time I read\ndocumentations (Under `Documentation` directory). `MyFirstContribution.txt`[1],\n`MyFirstObjectWalk.txt`[2] and `Hacking Git`[3] helped me to learn about the git\ncontribution workflow, how `git log` ( in other words `object walk`) works\ninternally.\n\nThough I had read many documentations, I was still not able to fully\nunderstand the terminologies (like `refs`, `packfiles`, `blobs`, `trees`\netc.). (ProGit)[https://git-scm.com/book/en/v2] helped me tremendously here.\nI read the full book and it cleared almost every doubt that came into my mind.\n\nI have provided my git involvement history below. Activities are sorted\nby timeline from top to bottom.\n\n==============================\nPRs, Commits & Discussion Participations\n==============================\n\n---------------------------------\n[patch] Amend error messages that violate git coding style convention\nGithub link : https://github.com/gitgitgadget/git/pull/1062\nStatus : Not Merged/ PR\nDescription : There are many error strings which do not follow coding\nstyle guides. This PR was to fix those. There is a ticket dedicated to\nthis ( github Issue - (#635)[https://github.com/gitgitgadget/git/issues/635]).\nThe author of this issue said it would be better to manually correct\nthese things.\nOutcome : As this was my first PR, I made many mistakes and I faced\ndifficulties. Though this was not merged, I learned tremendous new\nthings. These violating strings were in many files ( nearly 200 files).\nAt first, I fixed all the files at once manually. I fixed errors\ngenerated by those changes. Ultimately, I learned about overall git\nstructures, how to fix errors etc.\n\n---------------------------------\n[RFC PATCH 0/1] making set-upstream have default arguments\nMailing List : https://lore.kernel.org/git/20211202144354.17416-1-chakrabortyabhradeep79@gmail.com/\nStatus : Not Merged/ Closed\nDescription : `git push -u` generally ( if `push.default` not set)\nthrows an error if no arguments are provided. This patch request was to\nteach `git push -u` to push and set a default upstream if no arguments\nare provided. There is a github (issue)[https://github.com/gitgitgadget/git/issues/1061]\nalso.\nOutcome : This PR let `git push -u` to push to a default branch and\nset that as the upstream irrespective of `push.default` configuration.\nI realized it was badly affecting the reason `push.default` is built\nfor ( See this (comment)[https://lore.kernel.org/git/20220104132839.1209-1-chakrabortyabhradeep79@gmail.com/]).\nSo, I intentionally stopped working on it.\n\n----------------------------------\nAvoid checking for -h in commands that already use parse-options API ( Issue)\nGithub Issue Link : https://github.com/gitgitgadget/git/issues/1125\nStatus : Closed\n\n----------------------------------\n[PATCH] Add usage strings ci check and amend remaining usage strings\nGithub PR Link : https://github.com/gitgitgadget/git/pull/1147\nMailing List Link : https://lore.kernel.org/git/pull.1147.git.1645030949730.gitgitgadget@gmail.com/\nStatus : Merged into Master\nDescription : According to dscho’s (comment)[https://github.com/gitgitgadget/git/issues/636#issuecomment-1018660439],\nThere were still some usage strings that violated the style guide.\nSo, this patch request fixed those strings and added a CI check to\nverify all the usage strings are passing the style check. In the first\nversion, I built a shell script to check the validity of strings.\nOutcome : The first commit was merged into master. There were some\ncontradictions about the different approaches suggested by reviewers\nin the discussion about the last commit i.e. whether the check should\nbe static check or runtime check, whether I should use `parse options`\nmethod or coccinelle etc (see the (mailing list)[https://lore.kernel.org/git/nycvar.QRO.7.76.6.2202251632320.11118@tvgsbejvaqbjf.bet/]).\nLastly, it was decided that I should try the `coccinelle` method first\nand check if it is better ( see this (comment)[https://lore.kernel.org/git/20220304142154.2350-1-chakrabortyabhradeep79@gmail.com/]).\nI will try to submit a PR regarding this before April 19.\n\n==================================\nMicroProject\n==================================\n\n[PATCH] Partial-Clone : add a partial-clone test case\nGithub PR Link : https://github.com/gitgitgadget/git/pull/1175\nStatus : Merged into Master\nGithub Issue : https://github.com/gitgitgadget/git/issues/827\nDescription : In a blobless-cloned repo, `git log –follow – <path>`\n(`<path>` have an exact OID rename) shouldn’t download blobs of the\nfile from where the new file is renamed. This patch added a test case\nto verify it.\nOutcome : The test was added to the master branch. Moreover, another\nissue was discovered while discussing the patch request. Junio discovered\nthat the test helper function `test_subcommand_inexact` was poorly designed.\nLater Derrick submitted a (PR)[https://github.com/gitgitgadget/git/pull/1185]\nto fix it ( now merged).\n\n==================================\nReview\n==================================\n[PATCH] test-lib-functions : fix test_subcommand_inexact\nGithub PR Link : https://github.com/gitgitgadget/git/pull/1185\nDescription : Junio discovered that the `test_subcommand_inexact` function\n(test-helper function) is poorly designed. This PR addresses that.\nMy comment : Though I placed it under the `Review` section; but I didn’t\nreview the code here. Instead I gave my opinion regarding this in\n(this comment)[https://lore.kernel.org/git/20220324181056.53824-1-chakrabortyabhradeep79@gmail.com/].\n\n## Proposed Project\n\n### Abstract\n\nWhile sending large repositories, git has to decide what needs to be\nsent, how to be sent. For large repositories, git creates pack files\nwhere it packs all the related commits, trees, blobs( in the form of\ndeltas and bases ), tags etc. Now, finding the related objects among\nall the objects might be very expensive.\n\nAs git only knows about the branch tips, it is very expensive to find\nthe related objects from all the objects if we try to traverse down\nfrom the branch tips to all their respective related objects. It becomes\nmore expensive as the number of objects (i.e. commits, trees, blobs\netc.) increases. Ultimately resulting in slow fetching from the git\ndaemon.\n\nTo counter that, reachability bitmaps were introduced. It uses bitmap\ndata structure (an array of bits) to detect if an object is reachable\nfrom a particular commit or not. The commit messages of this\n(patch series)[https://lore.kernel.org/git/1372116193-32762-1-git-send-email-tanoku@gmail.com/]\nare itself a documentation of how it is achieved. All the bitmap\nindexes for selected commits (in a EWAH compressed form) are stored in\na `.bitmap` file which has the same name of its respective packfile.\n\nThe current task is to improve the performance of this bitmap approach.\nThere are three points that we need to work on -\n\n1. Decompression of bitmaps is slow with EWAH. To know if an object is\n   related to a particular commit, we have to decompress the whole thing.\n   So, we have to consider other alternative techniques besides EWAH.\n\n2. Loading a `.bitmap` file can be slow for large bitmaps. This is because\n   we need to read the file sequentially in order to discover the offset of\n   each bitmap within the file. It would be better if we can create a `table\n   of contents` for these bitmaps.\n\n3. Regenerating bitmaps can take a long time. One possible approach is to\n   add a new mode which only adds new bitmaps for commits introduced between\n   successive bitmap generations.\n\n4. If we solve the above points, we would think of other aspects like\n   rethinking how we select which commit receives bitmaps etc.\n\n### Previous Work\n\nI didn’t find any previous patches regarding point no. 1. But there were\nsome discussions about this. Derrick’s\n(comment)[https://lore.kernel.org/git/1685a358-f033-64e0-2e12-df3a1c10af19@gmail.com/]\nsuggested considering the\n(Roaring+Run)[https://roaringbitmap.org/about/]\ntechnique. It is much faster than the currently implemented\n(EWAH)[https://arxiv.org/abs/0901.3751].\n\nTaylor initiated the `developing a table of contents for bitmap` work\nby creating a\n(branch and committing some patches)[https://github.com/git/git/compare/master...ttaylorr:tb/bitmap-commit-table]\nin that branch. From the\n(discussion)[https://lore.kernel.org/git/YNuiM8TR5evSeNsN@nand.local/]\nand the performance test results provided in that discussion,  it seems\nthat it would improve overall performance. So, this would work as a\nreference for me while developing the table of contents for bitmaps\n(obviously after running performance tests and discussing the best\napproach).\n\n### Potential Problem\n\nThe biggest difficulty of this project would be to replace the EWAH\ncompression/decompression altogether with better techniques like the\nRoaring+Run method. I have to be aware of it so that it doesn’t\ngenerate any unintentional behavior or bugs.\n\n### The plan\n\nAs this project includes three ( actually four) sub projects, I would\naddress them one by one -\n1. Firstly I will understand the working of EWAH compression better.\n   I have gone through their documentation and have seen git’s\n   implementation code for it. The commit messages were really helpful\n   here. But I think I should research more. After that,  I can compare\n   (and discuss) each approach with respect to the EWAH approach on\n   some parameters (like amount of computation in each approach,\n   simplicity, memory usage, correctness i.e. does it always give the\n   correct output etc.). This comparison would lead me to take the\n   most ideal approach in this case. There are several techniques which\n   may work/perform better than the current EWAH implementation. I\n   have researched some of these techniques. One of them is obviously\n   the Roaring+Run method. I have gone through their\n   (research paper)[https://arxiv.org/pdf/1709.07821v6.pdf]\n   on this technique; it seems like a good approach to me. Other than\n   that, there is a golang package called\n   (sroar)[https://dgraph.io/blog/post/serialized-roaring-bitmaps-golang/]\n   (i.e. Serialized Roaring bitmaps), which is an open source package\n   ( mainly built for (Dgraph)[https://dgraph.io/])\n   and the creator of this package claims it is\n   (7x faster using 15x less memory)[https://github.com/dgraph-io/sroar#benchmarks].\n   It doesn’t require any encoding/decoding step. I would look into\n   it ( It needs to be implemented in C language though). I have also\n   looked into approaches like\n   (bloom filter)[https://en.wikipedia.org/wiki/Bloom_filter],\n   (Hyperloglog)[https://en.wikipedia.org/wiki/HyperLogLog]. These are\n   very fast and use very less memory. But they give probabilistic\n   answers and sometimes they may give wrong answers. So, those\n   would not be a good fit for us I guess.\n2. I will understand the bitmap related files such as\n   `pack-bitmap-write.c`[4], `pack-bitmap.c`[5] etc. It would\n   help me to decide where and how I can add the code related to\n   `table of contents` for bitmap.\n   Taylor’s (branch work)[https://github.com/git/git/compare/master...ttaylorr:tb/bitmap-commit-table]\n   would work as a reference for me. As the Project idea section\n   suggests, I would also include performance tests to continuously\n   check whether my approach is really improving the performance or\n   not.\n3. As I understand more about bitmap related files, I will surely\n   be able to think whether `adding a new mode` is really necessary\n   or not (It is conceptually a good idea though). If necessary,\n   then I would first make the flow design and discuss it with the\n   community. If all is good, I will start working on it. Creating\n   and running performance tests is a must.\n4. While developing all of these, my understanding of bitmap and\n   its implementation will get better. So, that would help me to\n   think more practically about the questions provided in the `Project\n   Idea` section. Then I would work on it accordingly.\n\n## Estimated Timeline\n\nMy Semester exams will most probably start from May last week. So,\nI may be inactive (or less active) that time.\n(Smart India Hackathon)[https://www.sih.gov.in]\n(semi finals and finals) may also be held during the GSoC event.\nI will get you notified about that.\n\n--> Period\n- Pre GSoC Period\n- Till May 20\n--> Tasks\n- Research more on the bitmap files, compression techniques etc.\n- See if there are any other (better) techniques for it.\n\n--> Period\n- Community Bonding\n- May 20 - June 12\n--> Tasks\n- Discussion on the project started\n- Decide which approach is better for compression/decompression of\n  bitmaps.\n- If a decision is not taken, create branches for each approach.\n- Create branches for each sub project and make skeletons for them.\n\n--> Period\n- Coding Phase 1\n- June 13 - July 25\n--> Tasks\n- Start working on sub-project no. 1 (i.e. bitmap compression\n  technique)\n- Add Performance test\n- If multiple branch are create for this sub-project, compare\n  the test results\n- Take the best performing approach, delete other branches.\n- Update documentation accordingly\n- Fix bugs\n- Finish sub-project 1\n\n--> Period\n- Coding Phase 2\n- July 25 - Sept 4\n--> Tasks\n- Fix sub-project-1 related small bugs\n- Start working on sub-project-2 (i.e. adding\n  `table of content` for bitmap files)\n- Add Performance test\n- Add Documentation\n- Fix bugs\n- If finished, start working on sub-project-3 (i.e. adding a\n  `new mode`)\n- Try to finish it with documentation and performance tests\n\n--> Period\n- Final Week 1\n- Sept 5 - Sept 12\n--> Tasks\n- If both are finished, fix bugs and test overall performance.\n  Else extend the period.\n- Discuss about the last sub project (i.e. questions )\n- If anything needs to be changed/modified or added, extend the\n  GSoC Period\n\n--> Period\n- Coding Phase 3\n- Sept 13 - Nov 13\n--> Tasks\n- Finish code related to all sub projects\n- Add overall documentation\n- Add overall performance tests\n\n\n## Blogging about Git\n\nI love to write blogs and technical articles. Those are my ways to\nconnect and communicate with the developers community. I have\npreviously written articles about Django in a portal named\n(GeeksForGeeks)[https://auth.geeksforgeeks.org/user/riter79/articles].\nRecently I started writing  blogs on\n(Medium platform)[https://medium.com/@abhra303].\n\nDuring the GSoC event, I will frequently write blogs about my\nprogress. I will also share the problems I face and the solutions\nof those problems that I consider.\n\nI got interested in git by reading Olga’s GSoC blogs. That led me\nto contribute to this codebase. So, someone like me will hopefully\nbe motivated by seeing my blogs ;-)\n\n## Availability\n\nI intentionally freed my summer slot for GSoC. So, there wouldn’t\nbe much disturbance/inactive days while working on my project.\nGenerally, I can spend nearly 35-40 hours a week on this project.\nIf the college gets closed for some reason, then the amount of\navailable time will increase. Smart India Hackathon finale would\nbe held in July. So, I may be inactive for a few days. But overall,\nI will be available most of the time.\n\n## Post GSoC\n\nOnce the GSoC finishes, I would look into other issues/tickets and\nwould send PRs solving those issues. As I said before, I want to\nbe a long term contributor to git - I would definitely maintain the\nflow and continue to work on improving the overall git tool.\n\n## Experience with Open Source\n\nI have a pretty good contribution history in open source. The\norganizations/tools where I contributed to are - \n\n - Mozilla/bedrock - written mainly in Python Django and javaScript\n   link - https://github.com/mozilla/bedrock/commits?author=Abhra303\n\n - Datree - a Kubernetes misconfiguration checker tool written mainly\n   in golang\n   link - https://github.com/datreeio/datree/commits?author=Abhra303\n\n - KubeBuilder - A tool to extend the Kubernetes API by creating custom\n   CRDs - written mainly in golang. I recently started looking into it.\n   link : https://github.com/kubernetes-sigs/kubebuilder/issues/2567\n\n## Motivation\n\nI always wanted to develop/contribute to projects that affect millions\nof people. Git is a tool that most ( or maybe every) developers\nuse for their daily work. Contributing to it means my written code\nwill be used behind the scenes in every developer’s machine. That’s my\nmotivation.\n\n## Closing Remarks\n\nLastly, I want to say that I am a dedicated, research preferred quick\nlearner. I am always ready to solve real world problems and learn\nrequired skills for them. For example, I recently took part in a\nhackathon called “Cloud Native Hackathon” and won 1st place in the\ncategory of “best use of Datree”. I knew nothing about\n(Datree)[https://datree.io/] ( and (Kubernetes)[https://kubernetes.io]\npartially) before this hackathon and the hackathon was only 2 days\nlong. But I researched hard ( to know the Kubernetes misconfigurations)\nand learned  jsonSchema ( Here is my\n(blog link)[https://medium.com/@abhra303/how-i-won-cloud-native-hackathon-2021-4b1f5b2a84f2]\nif you want to know my full experience).\n\nI hope you’ll give me a chance to make an impact among the developers\ncommunity by considering my application.\n\nThanks & Regards,\n\nAbhradeep Chakraborty\n\n\n\n[1] https://github.com/gitgitgadget/git/blob/master/Documentation/MyFirstContribution.txt\n[2] https://github.com/gitgitgadget/git/blob/master/Documentation/MyFirstObjectWalk.txt\n[3] https://git-scm.com/docs/user-manual#hacking-git\n[4] https://github.com/git/git/blob/master/pack-bitmap-write.c\n[5] https://github.com/git/git/blob/master/pack-bitmap.c\n"},{"id":"453589","messageId":"c2190b9c-3393-730d-1bed-d793c1d32275@gmail.com","threadId":"57682","inReplyTo":"20220406200959.27096-1-chakrabortyabhradeep79@gmail.com","subject":"Re: [GSoC][RFC][PROPOSAL] Reachability bitmap improvements","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2022-04-13T20:03:55Z","receivedAt":"2022-04-13T20:04:04Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hi Abhradeep,\n\nThanks for drafting your initial GSoC proposal. Some thoughts inline:\n\nOn 07-04-2022 01:39, Abhradeep Chakraborty wrote:\n>\n> I am Abhradeep Chakraborty, currently pursuing B.Tech in Information\n> Technology (now in my 3rd year) at Jalpaiguri Government Engineering\n> College, India.\n> \n> In the last two years, I mainly concentrated on learning and building\n> web development things. I mainly use Django, React for my projects. But\n> for the past 6 months, I have been learning about devops, cloud technologies\n> ( e.g. docker, Kubernetes, AWS etc.), computer networking and core\n> technologies (such as git, linux, gcc etc.). I also have an interest in\n> some research based technologies like WebRTC, Web3 etc.\n>\n\nThat's good to know. Do let us know if you have any experience with C\nand shell programming outside of your contributions to Git.\n\n> My ultimate objective is to be a dedicated and active contributor to all\n> of these technologies. So, I want to start this contribution journey with\n> `git` and therefore I want to be a part of this GSoC program.\n> \n> ## Me & Git\n> \n> I have started exploring the Git codebase since Sept 2021. At first, I\n> mainly focused on knowing the git internals. During this time I read\n> documentations (Under `Documentation` directory). `MyFirstContribution.txt`[1],\n> `MyFirstObjectWalk.txt`[2] and `Hacking Git`[3] helped me to learn about the git\n> contribution workflow, how `git log` ( in other words `object walk`) works\n> internally.\n> \n> Though I had read many documentations, I was still not able to fully\n> understand the terminologies (like `refs`, `packfiles`, `blobs`, `trees`\n> etc.). (ProGit)[https://git-scm.com/book/en/v2] helped me tremendously here.\n> I read the full book and it cleared almost every doubt that came into my mind.\n> \n> I have provided my git involvement history below. Activities are sorted\n> by timeline from top to bottom.\n> \n> ==============================\n> PRs, Commits & Discussion Participations\n> ==============================\n >\n > [ ... snip ... ]\n\nGood to see your various contributions to Git so far. Good work!\n\n> ## Proposed Project\n> \n> ### Abstract\n> \n> While sending large repositories, git has to decide what needs to be\n> sent, how to be sent. For large repositories, git creates pack files\n> where it packs all the related commits, trees, blobs( in the form of\n> deltas and bases ), tags etc. Now, finding the related objects among\n> all the objects might be very expensive.\n> \n> As git only knows about the branch tips, it is very expensive to find\n> the related objects from all the objects if we try to traverse down\n> from the branch tips to all their respective related objects. It becomes\n> more expensive as the number of objects (i.e. commits, trees, blobs\n> etc.) increases. Ultimately resulting in slow fetching from the git\n> daemon.\n> \n> To counter that, reachability bitmaps were introduced. It uses bitmap\n> data structure (an array of bits) to detect if an object is reachable\n> from a particular commit or not. The commit messages of this\n> (patch series)[https://lore.kernel.org/git/1372116193-32762-1-git-send-email-tanoku@gmail.com/]\n> are itself a documentation of how it is achieved. All the bitmap\n> indexes for selected commits (in a EWAH compressed form) are stored in\n> a `.bitmap` file which has the same name of its respective packfile.\n>\n\ns/indexes/indices/\n\n> [ ... snip ... ]\n >> ## Estimated Timeline\n>\n > [ ... snip ... ]\n\nTaylor has shared feedback on the proposal and timeline which I hope are \nhelpful to you. Specifically, Taylor said:\n\n> \n> So I think it makes sense to try and find a way you can dip your toes\n> into 2-3 of the sub-projects and get a sense for what feels most doable\n> and interesting, then focus on that before allocating time for more\n> projects in the future.\n >\n\nI agree with this. It's better to be practical than ambituous when \nplanning the proposal.\n\n> \n> ## Availability\n> \n> I intentionally freed my summer slot for GSoC. So, there wouldn’t\n> be much disturbance/inactive days while working on my project.\n> Generally, I can spend nearly 35-40 hours a week on this project.\n> If the college gets closed for some reason, then the amount of\n> available time will increase. Smart India Hackathon finale would\n> be held in July. So, I may be inactive for a few days. But overall,\n> I will be available most of the time.\n>\n\nThanks for letting us know of possible things that would interfere with \nGSoC! Do make sure to keep us posted in case you come to know of \nanything else.\n\n> ## Post GSoC\n> \n> Once the GSoC finishes, I would look into other issues/tickets and\n> would send PRs solving those issues. As I said before, I want to\n> be a long term contributor to git - I would definitely maintain the\n> flow and continue to work on improving the overall git tool.\n>\n\nThat's nice.\n\n--\nSivaraam\n"},{"id":"453644","messageId":"20220414082010.14217-1-chakrabortyabhradeep79@gmail.com","threadId":"57682","inReplyTo":"c2190b9c-3393-730d-1bed-d793c1d32275@gmail.com","subject":"Re: [GSoC][RFC][PROPOSAL] Reachability bitmap improvements","fromName":"Abhradeep Chakraborty","fromEmail":"chakrabortyabhradeep79@gmail.com","sentAt":"2022-04-14T08:20:10Z","receivedAt":"2022-04-14T08:20:40Z","isPatch":false,"sender":{"key":"chakrabortyabhradeep79@gmail.com","avatar":"https://avatars.githubusercontent.com/u/75240995?v=4"},"body":"Kaartic Sivaraam <kaartic.sivaraam@gmail.com> wrote:\n\n> That's good to know. Do let us know if you have any experience with C\n> and shell programming outside of your contributions to Git.\n\nThank you for reviewing my proposal. I used C language in my B.tech\nclasses. I never used C in practical/real world projects before. So,\nputting altogether, no, I didn't use C and shell in real world projects\nbefore.\n\n> Good to see your various contributions to Git so far. Good work!\n\nThanks.\n\n> s/indexes/indices/\n\nOops, correcting it.\n\n> > [ ... snip ... ]\n> >> ## Estimated Timeline\n> >\n> > [ ... snip ... ]\n>\n> Taylor has shared feedback on the proposal and timeline which I hope are \n> helpful to you. Specifically, Taylor said:\n>\n> > \n> > So I think it makes sense to try and find a way you can dip your toes\n> > into 2-3 of the sub-projects and get a sense for what feels most doable\n> > and interesting, then focus on that before allocating time for more\n> > projects in the future.\n>  >\n>\n> I agree with this. It's better to be practical than ambituous when \n> planning the proposal.\n\nOkay, I am willing to work on first sub-project then. Should I remove the\nother subprojects then?\n\n> Thanks for letting us know of possible things that would interfere with \n> GSoC! Do make sure to keep us posted in case you come to know of \n> anything else.\n\nYes! will surely inform you in that case.\n\nThanks :)\n"},{"id":"453671","messageId":"0179a76a-182a-0501-a4ae-800ddb53b8cd@gmail.com","threadId":"57682","inReplyTo":"20220414082010.14217-1-chakrabortyabhradeep79@gmail.com","subject":"Re: [GSoC][RFC][PROPOSAL] Reachability bitmap improvements","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2022-04-14T20:29:38Z","receivedAt":"2022-04-14T20:29:47Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"On 14-04-2022 13:50, Abhradeep Chakraborty wrote:\n> Kaartic Sivaraam <kaartic.sivaraam@gmail.com> wrote:\n> \n>> That's good to know. Do let us know if you have any experience with C\n>> and shell programming outside of your contributions to Git.\n> \n> Thank you for reviewing my proposal. I used C language in my B.tech\n> classes. I never used C in practical/real world projects before. So,\n> putting altogether, no, I didn't use C and shell in real world projects\n> before.\n>\n\nThat's good to know. Thanks.\n\n>> Taylor has shared feedback on the proposal and timeline which I hope are\n>> helpful to you. Specifically, Taylor said:\n>>\n>>>\n>>> So I think it makes sense to try and find a way you can dip your toes\n>>> into 2-3 of the sub-projects and get a sense for what feels most doable\n>>> and interesting, then focus on that before allocating time for more\n>>> projects in the future.\n>>   >\n>>\n>> I agree with this. It's better to be practical than ambituous when\n>> planning the proposal.\n> \n> Okay, I am willing to work on first sub-project then. Should I remove the\n> other subprojects then?\n> \n\nRather than deciding the plan in haste, I would recommend that you put \nsome more thought into deciding the plan for your proposal. Take some \ntime to reflect on the different parts required for the project, \npotential things that might interfere with the project etc. This would \nhelp you come up with a more refined plan.\n\nThis might need some deeper understanding of the project that you would \nbe working on. Do feel to ask us in case you face any issues with this.\n\nAlso, you could use Taylor's suggestion as a possible starting point for\nthe plan:\n\n > If you end up working on this, I would suggest budgeting a week or so\n > to try out a couple of different sub-projects, and then decide where\n > to spend your time from there.\n\nHope this helps,\nSivaraam\n"},{"id":"453681","messageId":"20220415052319.49380-1-chakrabortyabhradeep79@gmail.com","threadId":"57682","inReplyTo":"0179a76a-182a-0501-a4ae-800ddb53b8cd@gmail.com","subject":"Re: [GSoC][RFC][PROPOSAL] Reachability bitmap improvements","fromName":"Abhradeep Chakraborty","fromEmail":"chakrabortyabhradeep79@gmail.com","sentAt":"2022-04-15T05:23:19Z","receivedAt":"2022-04-15T05:23:49Z","isPatch":false,"sender":{"key":"chakrabortyabhradeep79@gmail.com","avatar":"https://avatars.githubusercontent.com/u/75240995?v=4"},"body":"Kaartic Sivaraam <kaartic.sivaraam@gmail.com> wrote:\n\n> Rather than deciding the plan in haste, I would recommend that you put \n> some more thought into deciding the plan for your proposal. Take some \n> time to reflect on the different parts required for the project, \n> potential things that might interfere with the project etc. This would \n> help you come up with a more refined plan.\n>\n> This might need some deeper understanding of the project that you would \n> be working on. Do feel to ask us in case you face any issues with this.\n>\n> Also, you could use Taylor's suggestion as a possible starting point for\n> the plan:\n>\n>  > If you end up working on this, I would suggest budgeting a week or so\n>  > to try out a couple of different sub-projects, and then decide where\n>  > to spend your time from there.\n\nGot it! thanks! Will do as you suggested.\n\nThanks :)\n"}]}