introduction

[Leila <muhtasib@gmail.com>]

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