[opensuse-project] Apply for GSOC 2013 under "Code review for projects on GitHub"

Hi, I am a Belgian student in Engineering at the Catholic University of Louvain-la-Neuve (UCL). I am 20 and currently in my second year of bachelor and I have token applied mathematics and computer science as options. I am familiar with Ruby on Rails, C/C++, Java, Android, Python and Oz. I am developing 2 websites in Ruby on Rails, one for managing vocabulary lists (https://github.com/blegat/openvoc) and one for training for mathematical olympiads (http://www.imo-official.org/) (https://github.com/blegat/ombtraining). For these 2 projects, I use RSpec, git and github. So I would say that I have a quite good experience with Ruby, Git and RSpec. I would love to contribute to git-review under the openSUSE umbrella. git-review is currently able to create a pull request from the CLI, list all pull requests, show it in the terminal, open it in a browser, get a local copy of the code, approve it, close it and merge it. According to the github issues of the project and the openSUSE idea's page, here a some improvements that could be done * Enable git-review to work on different forks of a project (it was on the idea's page, I don't really understand what it means, perhaps a summary of the issues about the tool being too upstream/master specific); * Use the latest GitHub API (v3); * Add support for Prophet which is a tool that "Loops through open pull requests on a GitHub hosted repository and runs your code (i.e. tests) on the merged branch. After the run has finished, Prophet will post a comment to the pull request stating whether the execution succeeded or failed."; * Continue the work being done to fully test git-review with rspec (https://github.com/b4mboo/git-review/issues/1); * Create requests to other repos and branches than upstream/master (https://github.com/b4mboo/git-review/issues/4); * The diffs are currently displayed against the local master, it would be nice to display it against master on github (https://github.com/b4mboo/git-review/issues/6); * Reviews are currently against master only except if the TARGET_BRANCH environment variable is set. I would be nice to find a more comfortable way to do this (https://github.com/b4mboo/git-review/issues/14); * Create pull request off from existing issue to avoid duplicate (https://github.com/b4mboo/git-review/issues/27). I find this tool very interesting and while its current state looks quite good, it still requires some work to be feature complete. However I don't think each of these feature would take so long to implement and I'm convinced that I will be able to implement all the items I've mentioned above during GSoC. Do you have any ideas of features I could add to/remove from the list ? I have found a similar tool for gerrit written in Python (https://github.com/openstack-infra/git-review), do you think that could be a good idea to make this tool compatible with both github and gerrit ? That way, it would be the same tool for both services for the developers. Do you think it is worth it or useless duplication of effort ? Thanks in advance :) Benoît Legat -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org

Hello, Am Sonntag, 14. April 2013 schrieb Benoît Legat:
I have found a similar tool for gerrit written in Python (https://github.com/openstack-infra/git-review), do you think that could be a good idea to make this tool compatible with both github and gerrit ? That way, it would be the same tool for both services for the developers. Do you think it is worth it or useless duplication of effort ?
IMHO it is worth the effort - otherwise we'll end up with git-review- github, git-review-gerrit, git-review-whatever, ... ;-) and "ideally" each of them has a slightly different syntax. You mentioned "duplication of effort", but I'd guess (without checking the code) that it could even be the other way round - the API of github and gerrit might be different, but for example the user interface shown to the person using "git review" can/should be the same for both backends, so you'll probably be able to avoid code duplication. Regards, Christian Boltz -- I've chosen Suse for over 10 years, despite knowing that my computer would be safest, enclosed in several feet of cement -- but it's really hard to use that way... ;-) [Linda Walsh in opensuse-factory] -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
participants (2)
-
Benoît Legat
-
Christian Boltz