Introductions!

I'm going to be learning git via my interest in Drupal. I'm very interested in helping to develop documentation on how to use git as a drupal contributor.

I've been using github (and thus git) to do ongoing module development before committing stuff to CVS, so I can help users with git basics at the very least. I tend to idle on irc, so I can help people there.

I've been using Git for about 6 months after switching from SVN. I am terribly good at breaking things, which is exactly why I had to stop using SVN. With Git, I seem to have a magical ability to also fix the stuff I break - which is nice.

I can help answer questions for people getting started, kick around ideas on GDO, and I'd even write a few docs or make screencasts.

Cheers!

I've used Git for all my own development for a few years, including anything I do with Drupal. I'm happy to help build the tools to make Git work on DO, and to help get users up to speed on Git.

I really like to help to get git working in d.o as soon as we can, I gonna do all I can from versioncontrol* modules and all other places :-)

I totally love git and using it some time ago, so I can help other people to learn about it.

I've been using Git for almost a year now. I've only been developing a little longer than that, so luckily someone told me about SCM early on, and I saw where that would come in handy. It's saved my hide at least a few times. I'm up to speed on using it as SCM, but the Distributed part hasn't really come into play for me yet. Until now...

I think I'd probably be most useful in a documentation role.

Hi All,

I saw the great presentation at Drupalcon SF about migrating from cvs to git. It was excellent. I'd love to help out where I can.

I've been using various version control systems for years, mostly svn. Then the buzz seemed to be around git and I switched to that for about a year. It was a long slow painful learning curve. I recently started using bzr but just before Drupalcon friends were saying I ought to switch back to git... so here I am.

I actually quite like git, I think it has neat features, including support for true branches, but there are definitely some gotchas, especially in the windows / *nix line ending conversion support.

I hope my year of learning to use git as a semi-technical user will be of use to the migration project. I especially look forward to helping with documentation.

Phil

Most of my experience has been with subversion but I have been experimenting with git for the past few months and trying to determine whether moving from svn to git is the right fit for my team. I think helping/learning with Drupal's transition is a great opportunity.

Kenny from Acquia here. I'm excited about learning more about Git and VERY excited about it taking over for CVS. I'd love to be a part of helping to write some accessible documentation for folks who are a) new to version control (specifically distributed) and b) new to contributing to open source projects like Drupal that use VC.

Ping me on here or in IRC and I can provide some assistance on the doc front to start. I am going to start digging deep into Git anyway over the next month or so, so I should be able to also assist with actual coder tasks as my understanding broadens.

Like Mike Booth, who sits about 20 feet from me, time is something I don't have a lot of. But I will make time to help with this huge step forward for our community.

-K

I've been using Git for all of my development work for a few years now. (In fact, it is the only VCS I've used with any regularity.)

I'm on IRC quite a bit and can help out there as questions come up.

I'm also interested in helping out with project module integration as needed though need to get up to speed on the code base first.

Finally, once we get in to the proposed "Phase 3+", I've got some ideas about integrating some kind of code review tool into the issue queue workflow. I think there are some really cool things we could do with this. For example, take a look at githubs code-review tool. You can even leave comments inline!. http://github.com/eojthebrave/drupal/commit/4a3837a2269a0b618a6208004d7d..., more info about the tool here http://github.com/blog/612-introducing-github-compare-view

I have been using git for a couple of years now. I use it for every personal project, including stuff like assignments and reports and I'm a fairly advanced user.
However, I have no clue whatsoever about the versioncontrol* modules or the project module. But, I have a certain "normal" experience of Drupal contrib modules and I'm willing to place all my 4 hands on deck for any help needed. I've been waiting a long time for this :-)

I haven't used it but have been looking at it for a bit now. I intend to help document it's uses from a Windows OS perspective and perhaps add helpful environment configurations using PowerShell that should make life easier for people. I will be introducing it at work with fellow script writers to help my understanding of how to use it.

Steven Peck
http://www.blkmtn.org

I started using git last july. I haven't been able to use it for work, but I use it for all my local projects & eojthebrave showed me the current git/drupal patch workflow.

I am not a git master, but hope to learn more about some of the advanced features. I can do basic workflow stuff, but I know git is more powerful.

Anyhow, this summer, I am teaching a git class as part of the Drupal Open Garden Project - I have to work out some of the details, but it looks like I will try to teach some remote participants, as well as some local participants. That class will happen after a basic 'command line' class - all in the first few weeks of July. I know we will try to focus more on the mentoring and real-time conversations. But I expect to be making some documentation soon & then also documenting 'remote git training.'

I am fairly obsessed with github and think that social coding projects are the wave of the future - so I am very interested in how we might move to git. I like the idea that every drupal user will have a limited git repo, and interested to see how the patch process will work out.

Very interested to think about how the code might get a more social framework around it (on d.o) - whether it be feeds of users recent commits, following other drupal users code, or making some taxonomies that might indicate where a newer user is at in their code-learning process. (Such as 'I learned: drupal php code standards, drupal js standards, using drupal api correctly, writing tests for my code, documentation, module contribution, core patching, patch reviewing)

Also interested in how people learn how to make their code ready to contribute. Would like to work on an in-between review process - where you can get advice for your project in a supportive environment (rather than just applying to share your code, waiting months and then having it rejected.) The new 'every user has a git repo' model will help with that, and it should be fun to document how to use it.

timewise - i will have some time to think about git in june/july, and then a few hours every month or so - and helping out at drupalcons and stuff like that. i am happy to organize local events to teach git if people have training ideas to try out.

I'm a long-time cvs and svn user and I'm now just starting to use git. I remember the hastle of first setting up a cvs account on d.o and doing my first commit and by helping with the git documentation I hope to be of help.

I currently use SVN to deploy to individual and multisite Drupal installs at work. New to git, but very interested in transferring the SVN deploy strategy to git with submodules. Would be happy to spend time testing the new systems and documenting.

Thanks much!
shrop

Every since I began to build web applications using Drupal, a version control system serving to unify the development and testing, staging and production instances of the product and to scaffold development strategy was part and parcel of my everyday workday, just as it had always throughout my software development career. It was CVS for a decade, then SVN for a decade, it is Git today and I am overjoyed at the decision to adopt Git in the Drupal Project, not just because it is what I have adopted but also because of the immense possibilities it opens.

When I wrote my book Leveraging Drupal two years ago, it was my intention to share with people how they could set up a serious Drupal shop or at least development environment. I am not planning on writing any more books, but I do a lot of mentoring and free community courses in the Buenos Aires Drupal user's group, and just as drush, SVN and other serious tools were part of what I recommended and taught in the past, using the new Drush, and Aegir, and Git, the new paradigm in version control, will now feature prominently in what I want to be sharing.

The focus there has to be how Git brings in a new paradigm as a distributed version control system, and how you can do so much more with Git than you could with earlier tools, above and beyond the switch to Git itself, which is our main concern here in this group.

Big fan. Been using Git for the last year on Drupal projects - mostly on GitHub and Assembla, though not in a fully distributed model (my team all commits to a central repo). We've just started using Git submodules and I'm loving concept of being able to manage external dependencies, though I can't wrap my mind around the full implications of submodules. I'm curious about how submodules might work their way into Drush Make....

Anyway, not an expert but really happy to help out answering (and well, asking) n00b questions.

Cheers,
Sean Larkin
ThinkShout.com

I'm no wizard at Git, but I'm getting there. I don't have much time, but I've been working with some of the low hanging fruit. I also kind of patrol the issue queues and try to find poorly named or wrong category issues.