introduction

introduction

[Leila]

Hi everyone,

I'm attending Hacker School and was interested in contributing to git
this summer and possibly afterwards. At Hacker School they encourage
us to contribute to open source software and projects were are
interested in. I'm in love with git, so naturally I want to contribute
to you guys. Why git? Because it's an awesome tool that has many well
thought out features that other source control tools lack like offline
mode. I'd like to see more people using git, and I'd like to see it
chosen as the source control tool used for team projects. So I was
thinking about contributing the following (which are the reasons I've
heard why people don't use git):

1) Commands are cryptic: I was thinking I could provide a wrapper to
simplify the commands, for example to undo a local commit, I can
introduce a "git undo commit", that wraps "reset" and will undo the
last commit. Or maybe "git rollback" is a better name?

2) git undo command, that will undo the last command (if possible)?

Other ideas:

3) Just like we have git-svn, maybe a svn-git?

Any help or if you can point me in the right direction, I'd appreciate
it. I can also start out by fixing some bugs to get into it. I
couldn't figure out how to see a list of bugs though.

How does one contribute to your documentation? Would it be submitting
a patch just like with code?

Please let me know what you think!

Thanks,
Leila

Re: introduction

[Michael Schubert]

On 06/04/2012 10:36 PM, Leila wrote:
> 1) Commands are cryptic: I was thinking I could provide a wrapper to
> simplify the commands, for example to undo a local commit, I can
> introduce a "git undo commit", that wraps "reset" and will undo the
> last commit. Or maybe "git rollback" is a better name?

There's Legit [1], Easy Git [2] and probably more.

> 2) git undo command, that will undo the last command (if possible)?

Not possible in general.

> 3) Just like we have git-svn, maybe a svn-git?

?

> Any help or if you can point me in the right direction, I'd appreciate
> it. I can also start out by fixing some bugs to get into it. I
> couldn't figure out how to see a list of bugs though.

There's no bugtracker, just the ML.

How to submit patches:
https://raw.github.com/gitster/git/master/Documentation/SubmittingPatches

You could check "old" GSoC Ideas:
https://github.com/peff/git/wiki/SoC-2012-Ideas

> How does one contribute to your documentation? Would it be submitting
> a patch just like with code?

Yes.

HTH.

[1] http://www.git-legit.org
[2] http://people.gnome.org/~newren/eg/

Re: introduction

[Andreas Ericsson]

On 06/04/2012 10:36 PM, Leila wrote:
> 
> 3) Just like we have git-svn, maybe a svn-git?
> 

I would absolutely love "gvn" command that works more or less exactly
like svn, but works against a git repository instead. That might allow
me to persuade the last recalcitrant bugger to switch to a version
control that actually allows people to work *with* the tool instead of
*for* it.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

Re: introduction

[Leila]

On Tue, Jun 5, 2012 at 5:04 AM, Michael Schubert <schu@schu.io> wrote:
> On 06/04/2012 10:36 PM, Leila wrote:
>> 1) Commands are cryptic: I was thinking I could provide a wrapper to
>> simplify the commands, for example to undo a local commit, I can
>> introduce a "git undo commit", that wraps "reset" and will undo the
>> last commit. Or maybe "git rollback" is a better name?
>
> There's Legit [1], Easy Git [2] and probably more.

Ok fair.

>
>> 2) git undo command, that will undo the last command (if possible)?
>
> Not possible in general.

Undoing adds and commits? But I guess there isn't a long list here..

>> 3) Just like we have git-svn, maybe a svn-git?
>
> ?
>
>> Any help or if you can point me in the right direction, I'd appreciate
>> it. I can also start out by fixing some bugs to get into it. I
>> couldn't figure out how to see a list of bugs though.
>
> There's no bugtracker, just the ML.

Thanks!

> How to submit patches:
> https://raw.github.com/gitster/git/master/Documentation/SubmittingPatches
>
> You could check "old" GSoC Ideas:
> https://github.com/peff/git/wiki/SoC-2012-Ideas

Thanks I've reached out to Peff and Thomas.

>> How does one contribute to your documentation? Would it be submitting
>> a patch just like with code?
>
> Yes.
>
> HTH.
>
> [1] http://www.git-legit.org
> [2] http://people.gnome.org/~newren/eg/
>

Re: introduction

[Leila]

On Tue, Jun 5, 2012 at 5:40 AM, Andreas Ericsson <ae@op5.se> wrote:
> On 06/04/2012 10:36 PM, Leila wrote:
>>
>> 3) Just like we have git-svn, maybe a svn-git?
>>
>
> I would absolutely love "gvn" command that works more or less exactly
> like svn, but works against a git repository instead. That might allow
> me to persuade the last recalcitrant bugger to switch to a version
> control that actually allows people to work *with* the tool instead of
> *for* it.
>

Yea, that's exactly the same reason I had. I wanted my colleagues to
switch to using git from svn. I love the name you gave it. That's
totally the name that project should be.

> --
> Andreas Ericsson                   andreas.ericsson@op5.se
> OP5 AB                             www.op5.se
> Tel: +46 8-230225                  Fax: +46 8-230231
>
> Considering the successes of the wars on alcohol, poverty, drugs and
> terror, I think we should give some serious thought to declaring war
> on peace.