This post originated from an RSS feed registered with Java Buzz
by News Manager.
Original Post: Make Git work for global teams
Feed Title: JavaWorld
Feed URL: http://www.javaworld.com/index.rss
Feed Description: JavaWorld.com: Fueling Innovation
It starts small. One curious user downloads Git to see what all the fuss is about. Before long he’s extolling its virtues to his buddy, and they start pushing/pulling work back and forth. Next comes the developer version of a grassroots movement to use Git on more projects. Sure, various challenges pop up, but there are tools on the market and workflows that help assuage Git’s initial growing pains.
When you go global, however, things get messy. It’s easy enough to rely on various Git hosting approaches when everybody’s connection is in the same geographic area. But what do you do when your developers and other stakeholders who need to contribute content to the project are scattered around the world? I recently heard a customer of ours explain that they literally cannot bring all the talent together required for a new product on a single continent. That’s a scary thought.
Previous Topic
