Hi, On Sun, Mar 18, 2018 at 11:15 PM, Paul Sebastian Ungureanu <ungureanupaulsebastian@xxxxxxxxx> wrote: > Hello, > > I am interested in the "Convert scripts to builtins" project. I have > recently started to analyze it better and see exactly what it entails > and a few questions came to my mind. Great! As other potential GSoC students are also interested I'm adding them into Cc. > First of all, I find it difficult to pick which scripts would benefit > the most by being rewritten. I am thinking of git bisect, git stash > and git rebase since these are maybe some of the most popular commands > of Git. However, on the other side, scripts like > git-rebase--interactive.sh and git-bisect.sh are also subject of other > GSoC projects. Should I steer away from these projects or can I > consider them? If you are interested in converting these scripts, you should probably ask publicly to the former GSoC students who have been working on these projects if they still plan to continue working on them of if they are ok to let you finish/continue their work. You will get extra bonus points if they agree to help you or maybe co-mentor you. > Secondly, what is too little or too much? On one hand, I do want to do > my best and help the Git community as much as I can. On the other > hand, I do not want to have too much on my plate and not be able to > finish my project. Considering that mentors have already decided that > git rebase --interactive and git bisect are enough for two projects, > how could I quantify the time required for each command? Looking back > at the previous editions of GSoC I noticed that most projects were > focused on only one command. Yeah, I don't think it is a good idea to focus on more than one command per project. It could be possible if there were really small scripts to convert, but I think those have been already converted. It could perhaps be possible if 2 scripts were very similar, but I don't think there are similar enough scripts to convert. You can however submit more than one proposal, so you could for example submit one proposal to convert one script and another one to convert another script. > From my research, these are the scripts that could be subject of this > project. Which ones do you think could be the best choice for a > project of this kind? I think it is definitely a good idea to work on a script that has started to be converted. Make sure that no one is still actively working on converting it though. I think the scripts related to other versions control systems are not a good choice as they are not really part of the core of Git. It is also a good idea to choose scripts that potential mentors are familiar with. > * git/git-add--interactive.perl > * git/git-archimport.perl > * git/git-bisect.sh -- there is a project about this > * git/git-cvsexportcommit.perl > * git/git-cvsimport.perl > * git/git-cvsserver.perl > * git/git-difftool--helper.sh > * git/git-filter-branch.sh > * git/git-instaweb.sh > * git/git-merge-octopus.sh > * git/git-merge-one-file.sh > * git/git-merge-resolve.sh > * git/git-mergetool--lib.sh > * git/git-mergetool.sh > * git/git-quiltimport.sh > * git/git-rebase--am.sh > * git/git-rebase--interactive.sh -- there is a project about this > * git/git-rebase--merge.sh > * git/git-rebase.sh > * git/git-remote-testgit.sh > * git/git-request-pull.sh > * git/git-send-email.perl > * git/git-stash.sh > * git/git-submodule.sh -- there was a project about this > * git/git-svn.perl > * git/git-web--browse.sh It would be interesting to know the number of lines of code for each of these script, as it could give an idea about how big the task of fully converting the script could be. > I look forward to hearing from you. I will also submit a draft of my > proposal soon enough. Great! Christian.
