Hello, I have completed the first draft of my proposal for the Google Summer of Code, which can be found at [1] or below for those who prefer the text version. Any feedback is greatly appreciated. Thanks! [1] https://docs.google.com/document/d/1TtdD7zgUsEOszHG5HX1at4zHMDsPmSBYWqy dOPTTpV8/edit?usp=sharing Best regards, Paul-Sebastian Ungureanu # Convert “git stash” to builtin # Name and Contact Information Hello! My name is Paul-Sebastian Ungureanu. I am currently a first year Computer Science & Engineering student at Politehnica University of Bucharest, Romania. My email address is ungureanupaulsebastian@xxxxxxxxx and my phone number is [CENSORED]. You can also find me on #git IRC channel as ungps. FLOSS manual recommends students to include in their proposal their postal address and mention a relative as a emergency contact. My permanent address is [CENSORED]. In case of an emergency, you may contact my brother, [CENSORED] by email at [CENSORED] or by phone at [CENSORED]. # Synopsis Currently, many components of Git are still in the form of Shell or Perl scripts. This choice makes sense especially when considering how faster new features can be implemented in Shell and Perl scripts, rather than writing them in C. However, in production, where Git runs daily on millions of computers with distinct configurations (i.e. different operating systems) some problems appear (i.e. POSIX-to- Windows path conversion issues). The idea of this project is to take “git-stash.sh” and reimplement it in C. Apart from fixing compatibility issues and increasing the performance by going one step closer to native code, I believe this is an excellent excuse to fix long-standing bugs or implement new minor features. # Benefits to community The essential benefit brought by rewriting Git commands is the increased compatibility with a large number computers with distinct configuration. I believe that this project can have a positive impact on a large mass of developers around the world. By rewriting the code behind some popular commands and making them “built-in”, developers will have a better overall experience when using Git and get to focus on what really matters to them. As a side effect, there will be a number of other improvements: increased performance, ability to rethink the design of some code that suffered from patching along the time, have the chance to create new features and fix old bugs. In theory, switching from Bash or Shell scripts, Git will be one step closer to native code which should have a positive impact on the performance. Being able to start from a clean slate is a great opportunity to rethink old designs that may have been patched a lot during their lifetime. This way, with the help of my mentors, I can think of new ways to try and remove some limitations of the current system (if there are any). Moreover, I believe that the community will benefit greatly from new features and bug fixes that I could help with. Even though this is not really one of the main goals of this project, I believe that it would be easier to fix bugs or implement new features while rewriting the code. However, I will have to discuss with my mentors and carefully review issues as I would not want to divagate from the purpose of the project. As a last point, I believe it is good to have a more homogenous codebase, where the majority of the code would be written in C. This could increase the number of contributions to the project as there are maybe more programmers who are familiar with C, and not so much with Perl or shell scripting. # Deliverables Deliverable of this project is “git stash” completely rewritten in portable C code. Along with the new code, there will be some additions and changes brought to tests to cover any new behaviour. # Related work Looking over the list of the other proposed projects, I believe that “Convert interactive rebase to C” and “git bisect improvements” are the most alike with this project and may be stretch goal of this project. Moreover, there is a chance that other scripts could benefit from this project if it were to be taken as an example for future conversions. # Biographical information I am a freshman at Politehnica University of Bucharest, which is considered to be one of the most prestigious universities in the Eastern Europe. I consider myself an ambitious software engineer that enjoys competition. This has been proven by my participation to programming competitions and extracurricular projects. As much as I like competitions, I also love working with and meeting people that share my interests for programming and technology. Even though, in the last two years I found myself to be more interested in Android software development rather than competitive programming, I still take part in most of the competitions, such as contests organized by Google HashCode, Google KickStart and ACM. I have a good grasp of programming languages such as C and C++ and I consider both of them to be my favorites. In the past, I intensively used shell scripting and Git for some of my personal projects. One of the facts that motivates me the most is that I get the chance to improve my abilities by getting the code reviewed by professionals that have been in the industry for a long period of time. This way, I get first-hand experience regarding software management and increase my programming skills in a professional environment. Ultimately, I believe that being part of a community such as Git would be a great confidence boost for me knowing that I gave something back to an excellent piece of software that I am using on a daily basis. # Project Details * Plan for converting each command * Understand the command well: read documentation, discover any features I were not aware of, find out how it works and why it works that way. * Find out all edge and corner cases: these should be quite obvious as soon as I have a good understanding of how the command works. * Find out the history of the command and what future improvements can be made: history of the command will help me know what issues affected the command, how those issues were fixed and will help me avoid them in the future. As I mentioned before, I believe that reimplementing those commands is a great excuse to fix bugs and if there are any, I need to know about them. * Convert function: this step is basically makes up the goal of this project. * Ensure that no regression occurred: considering that there are plenty of tests and that I have a good understanding of the function, this should be a trivial task. * Finally write more tests to ensure best code coverage. # Potential difficulties during conversion The rewritten code may introduce new bugs that may be delaying the project. I believe there is a small chance this will happen as long as I spend some time first to fully understand how it works and why it works that way. Considering the amount of documentation already available and the discussions from the mailing list, this should be a trivial task. Moreover, I am already familiar with “git stash”. There may be old bugs, from the Shell scripts that would cause issues while porting because they would probably require a discussion about what implications the bug has and what is the best way to fix it. Most of the times, Shell scripts tend to be a lot more smaller and hide a lot of complexity. Moreover, new data structures or utility functions may be needed, some which exist and need changes or do not exist and need to be implemented from scratch. # Wrapping-up the project In the end, the old Shell script will serve only as a called to the stash-helper I would be implementing. The final step is to remove the Shell script and promote the stash-helper to stash builtin. # Useful resources There has been a lot of progress made in this direction already and I believe it will serve of great help. However, from my understanding it is not yet mergeable and it requires changes. https://public-inbox.org/git/20170608005535.13080-1-joel@xxxxxxxxxxxxx/ T/#m8849c7ce0ad8516cc206dd6910b79591bf9b3acd # Project Schedule I can spend about 25 hours during the exam period (last half of May and the first half of June) and about 40 hours a week as soon as I am done with exams. I hope that by the start of the program (14th of May), I will have completed a good part of the project and that will compensate for the exam period. After Google Summer of Code ends, I will do my best to keep contributing to Git. Hopefully, all the work I proposed over the summer will be done and I will be able to move towards other areas, maybe by continuing converting other scripts to builtins or something else, depending on what are the priorities of the Git team. Google Summer of Code starts on 14th of May and lasts 13 weeks. I propose to convert one command per week. I actually do not expect each command to take exactly one week, some may be easier to convert and other may be more challenging, but I believe that the average time of conversion is around 1 week. I am expecting to submit a patch for every command that is converted. This way, I have well set milestones and results will be seen as soon as possible. Moreover, seeing my contributions getting merged will be a huge confidence boost to myself. Each “convert” phase of the project below is not only about converting from Shell to C, but also ensuring that everything is documented, there are enough tests and there are no regressions. 14th May - 20th May - Convert "git stash list" 21st May - 27th May - Convert "git stash show" 28th May - 3rd June - Convert "git stash save" 4th June - 10th June - Convert "git stash push" 11th June - 17th June* - Convert "git stash apply" 18th June - 24th June - Convert "git stash clear" 25th June - 1st July - Convert "git stash create" 2nd July - 8th July - Convert "git stash store" 9th July - 15th July* - Convert "git stash drop" 16th July - 22nd July - Convert "git stash pop" 23rd July - 29th July - Convert "git stash branch" 30th July - 5th August - Remove old Shell script. 6th August - 12th August* - Wrap-up the project by writing more tests and documentation. 12th August - forever - Pick up another project. * 1st, 2nd and 3rd mentor and student evaluation # Git contributions My first contribution to Git was to help making “git tag --contains <id>” les chatty if <id> is invalid. Looking over the list of available microprojects, there were a couple of microprojects which got my attention, but I picked this up because it seemed to be a long-standing bug (I noticed it was approached by students in 2016, 2017 and now in 2018). Thanks to the code reviews from the mailing list, after a few iterations I succeeded in coming up with a patch that not only fixed the mentioned problem, but also a few others that were having the same cause. It got merged in the proposed updates branch. I worked on only one project because I tried to achieve the best quality I could. Even after I submitted one patch that was good enough [7], I decided to try another approach that worked better in the end [8]. First of all, I weighed the ideas mentioned at [9] and considered the second one to be the best. After a few iterations [1], [2], [3], [4], [5] and after Junio’s review I decided to try another approach and submitted another patch [6]. I changed the approach, because this issue was affecting not only “git tag” command, but also “git for-each-ref”, “git branch” and many more. The new submission was based on Junio’s ideea and fixed the cause at a lower level than the previous patch. In order to make sure that the new code was 100% correct and familiarize myself with the testing system, I also write a new set of tests. [1] https://public-inbox.org/git/20180219212130.4217-1-ungureanupaulsebasti an@xxxxxxxxx/ [2] https://public-inbox.org/git/20180223162557.31477-1-ungureanupaulsebast ian@xxxxxxxxx/ [3] https://public-inbox.org/git/20180303210938.32474-1-ungureanupaulsebast ian@xxxxxxxxx/ [4] https://public-inbox.org/git/20180306193116.23876-1-ungureanupaulsebast ian@xxxxxxxxx/ [5] https://public-inbox.org/git/20180319185436.14309-1-ungureanupaulsebast ian@xxxxxxxxx/ [6] https://public-inbox.org/git/20180320175005.18759-1-ungureanupaulsebast ian@xxxxxxxxx/T/#u [7] https://public-inbox.org/git/xmqqpo4ne8ud.fsf@xxxxxxxxxxxxxxxxxxxxxxxxx / [8] https://public-inbox.org/git/xmqqefkm6s06.fsf@xxxxxxxxxxxxxxxxxxxxxxxxx / [9] https://public-inbox.org/git/20160118215433.GB24136@xxxxxxxxxxxxxxxxx.n et/
