Building Drupal projects on Git
Building a Drupal project using git is different than building Drupal itself, and requires its own workflow. I've been kicking ideas back and forth with Sam Boyer lately about how to make this process take advantage of all the Git power, but also be newbie-safe and as frictionless as possible. I think what we've come up with is pretty good: there's even code written! The process I am going to explain allows the following:
- Git-based updates for Drupal core and contrib
- The ability to patch/tweak core/contrib without the complexity of vendor-branches
- Portability for local development or Git-based deployment
- Unrestrained custom development: feature branches, tags, multiple repos
- Safe patterns that minimize conflicts and provide a clear resolution process
Pretty cool, eh? Expect a larger manifesto post from Sam in the near future, but for now here's where we are heading.
Read moreWant to learn more about GIT?
In case you missed it, Randy Fay (rfay), posted that there will be live training & support sessions for Git. Are you a maintainer that hasn't gotten on the Git bandwagon yet? Are you curious about why Git rocks? Then these live training sessions are for you. Please note that I simply noticed his post & wanted to share w/the LA Drupal community in case others have missed it (the 1st one is next week).
http://groups.drupal.org/node/130014
More good news! They're using Webex for the live stream which means there's the usual support for Windows & Mac but ALSO Linux support & even Solaris!
Read moreCollaboration on GitHub
I've created an Organization on github for our projects that we would like to work on with each other. It can be found here: https://github.com/lvdug ... please comment with your github username so I can add you as a member of the organization.
Read moreAegir rebels now consider migrating back to drupal.org - some questions...
Aegir migrated away from Drupal.org more than a year ago because it needed git magic to do proper maintenance of its code (but also wanted to merge the modules in the install profile to simplify maintenance). Now that Drupal.org is migrating to git (yaaaay! thank you!), we're reconsidering that decision, and have opened the discussions on our forum to see if that would be a good idea: http://community.aegirproject.org/node/369
My main questions to you guys are those two:
Read moreDrupal Git Logo
The Great Git Migration now has a logo, a gitified Druplicon.
This is @DrupalGitGremln 's icon on twitter.
(Organizers of this group: can you set an icon for a group? If so, this we be good.)
Read moreGit workflows for a Drupal shop
Now that Drupal is making the move to Git, I imagine lots of Drupal shops will be too. Ours is definitely among them.
Read moreJanuary Meeting: Git with Drupal 7
DRIOMETRICS: An Idea for Automating Identification of Duplicate Modules
I have an idea for dealing with duplicate modules at a more (but not fully) automatic level.
As I understand the problem duplicates are caused by one of the following situations:
Read moreConsistent approaches to git documentation for site builders
I have been reviewing the various documentation (http://drupal.org/node/803746) and blog posts oriented towards site builders on this topic over the last few days, and it seems there are many very different recommendations a approaches to building sites with git. There is an opportunity here to shape some best practices that will both make everyone's lives easier in the long run, but also encourage contribution back to the community as a standard part of building any Drupal site.
Read moreIMPORTANT: Source code, projects, and commit access in a post-Git world
(TL;DR? Here's summary #1: http://groups.drupal.org/node/114264#comment-367134)
For those who have not been following along with the CVS -> Git migration progress, this post contains important information for you to be aware of.
Things that we know:
- Once Git launches, anyone with a Drupal.org account will be able to commit code to Drupal.org.