git

Hi
I would like to suggest a casual meetup in Beijing to get connected and network and share.

Also I learned how to contribute back to the community even though I am not a drupal expert(I am a little over 4 months since discovering drupal).
I would like to share things I learned from community members when I attended DrupalCon Munich recently and share my experience if you are interested in hearing.
-How to setup local setup for drupal core 8.
-installing git
-how to contribute and help on drupal 8 issues/reviews
Check drupalladder.com for more info.

Buenas a todos,
Soy nuevo con git despues de mucho tratear con centos he conseguido clonar remotamente y subir.
pero tengo un problema es que cuando clono no lo hace con los permisos actuales del ultimo momento, lo hace con los del principio no se por que un saludo

We held our Broward Drupal monthly meetup on Wednesday, May 9th from 7:00pm to 9:00pm.

Remote participant(via Skype):
Seattle - Chris Parsons @chillin411

In Person (Greater Fort Lauderdale, Broward County Florida):
Jay Epstein @jeppy64
Rob de Koter @Robdekoter
John Everett @Agile_dot_TV
John Dennison @JohnDennison
Jeff Locke (adoptek.com)
Tony Webb
Elvis Svoboda
Samantha Jackson
Shevlin Pierce
Me @hectoriribarne

I need help understanding the workflow for database version control because what I am doing now is not working.

When I am on a branch (1), and about to commit, I do a Drush @alias sql-dump, which creates a dump file in a particular directory in my repo and uses a specific name, per instructions in the aliases.drushrc.php file. Then I commit and the sql-dump is added to the commit. I see the messages and everything is working fine.

Abstract

Although Drupal has switched to Git for its Version Control needs for about an year, yet the workflow is by and far patch based, when it comes to collaborating. While some choose the path of creating sandboxes and then create an issue in the main project, yet we are far from using the power of distributed workflow that Git offers us. The following proposal aims at providing the base of using Git-like workflow while collaborating on projects.

Previous Discussion(Summary)

The detailed description of repo-families can be found here[2].

Abstract

The Version Control API is an engine for Drupal integration with a variety of version control systems. It delivers an interface to these systems for use with various development-oriented modules, like Project.

There should still be some review process after one is given full git access, as there are many people who take it in wrong sense & put modules as which are not may be required.
Just some review process so that same quality which is checked while approving project applications during giving git access can also be maintained later.
Do we really require those projects which may not follow standards to be there ?
Like http://drupal.org/project/contact_profile
No offense, but is it fine to put a module with minimal code [e.g. drupal_alter just] as full project?

Last night while I was demoing, someone mentioned the colors I had on the command line and how it also denoted which GIT branch I was in. You can thanks James Sansbury (q0rban) for the code.

My instructions are biased towards MAC users. Sorry.

You need Git already installed for this to work.

In your terminal... //denotes my comments

//Find where your bash file is
ls ~/.bash_profile

//This returns "/Users/miche/.bash_profile" for me
//change directory (cd) to that path
cd /Users/miche

//Make sure you are there by "print working directory"
pwd

Do we have any Git Guru's in our bunch? I'm learning Git by a firehose and there are something things that I haven't yet wrapped my brain around. I would love a hands-on show and tell session with some people if anyone is interested? I would be up for a virtual meeting before the meetup in January.

I'm attempting to make several development paths within my repository and I am not 100% sure I'm doing it right to make sure all the paths stay up-to-date on the master branch changes.

Hello everyone,

I have been "messing" with drupal for a while now, and have now taken my first job as a 100% committed Drupal developer & tech lead for a company that builds massive websites for large federal initiatives that involve dense structures, complex role management schemes, and mountains of content (often 10,000+ nodes).

So, one of my first tasks as we get started is to work with the site building team and sys admins to create a solid process for performing migrations from dev >>> staging, sometimes staging >>> dev, and, of course, the eventual staging >>> production.