Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jgit-dev] GSoC 2012 Ideas

2012/3/23 Vipul Amler <vipulnsward@xxxxxxxxx>
On Thu, Mar 22, 2012 at 8:55 PM, Tomasz Zarna <tzarna@xxxxxxxxx> wrote:
> Cool, I've added the idea under
> Feel free to tweak it if you think it requires some clarification.

I am Vipul A M, a final year Comp. Sci. student. I was interested to
work on JGit for GSoC, and had posted before. I see some action here,
so posting again.

I am currently working with JGit on two of my projects,

* one which only made use of the JGit API to provide nice Web-Interface.
* in the other one I had to make changes and add a command to the API,
and pgm CLI, and work with the clone-pull-fetch and pack-level jobs.

I would be interested to work on translating pgm CLI switches/commands
and vice-versa,
But I have been lazy with JGit tests.

this will have to change if you want to contribute to JGit as we want
tests for everything. So it's a good chance to get rid of this kind of laziness.
You'll learn that in the end it's more lazy to care for a good test coverage as 
this way you'll waste less time fixing bugs.
Waiting to hear more, on this.

> Cheers,
> Tomek
> On Thu, Mar 22, 2012 at 15:00, Matthias Sohn
> <matthias.sohn@xxxxxxxxxxxxxx> wrote:
>> 2012/3/22 Tomasz Zarna <tzarna@xxxxxxxxx>
>>> Hi guys,
>>> I noticed that there is no section for JGit/EGit ideas [1] on this
>>> year's edition of GSoC [2].
>>> A proposal I have in mind is to tackle bug 365439 [3], which is about
>>> adding new CLI commands to the o.e.jgit.pgm project and vice versa ie
>>> translating some of the existing CLI commands/switches to JGit API.
>>> This would make CLI tests[4] more usable, but also it would boost
>>> development of the git console in Orion[5]. Optionally, the student
>>> could help me speeding up work on randomized JGit tests[6]. I have a
>>> rough draft for that but spending like 60 mins a week will take me
>>> ages to finish :)
>>> Since I don't have commit rights in JGit, all I can offer is
>>> co-mentoring and reviewing eventual patches first before asking for a
>>> second opinion of somebody with the commit rights (a second mentor).
>>> Does it make any sense to you? Is it ok to add that proposal to the list
>>> [1]?
>> sounds reasonable to me, I registered as a GSoC mentor so if there is a need
>> for another mentor I can offer my help
>>> Cheers,
>>> Tomek
>>> [1]
>>> [2]
>>> [3]
>>> [4] o.e.jgit.pgm.test, added in
>>> [5]
>>> [6]
>>> _______________________________________________
>>> jgit-dev mailing list
>>> jgit-dev@xxxxxxxxxxx
>> --
>> Matthias
> _______________________________________________
> jgit-dev mailing list
> jgit-dev@xxxxxxxxxxx
jgit-dev mailing list


Back to the top