Auto-syncing code repositories country wise - version-control

So our development team is spread across multiple countries and code repository is hosted in United states.
Now Problem is except U.S, commits & pull from other countries take too much time.
Is there any way we can host code repository country wise and it ll auto-sync to seem like one(having commits and changes from all countries)?

Related

How to manage large number of repositories on github?

I am student and I so far I have been using Github for keeping all of my projects. But the number of repos is growing and it is getting hard to manage. Is there a way to group repositories in something like folders, or is there some other service than Github, where I can do just that?

Is it possible to compare Github users? Specifically their contributions?

The company I work for uses GitHub extensively. Is there is a way to compare my team's individual contributions to specific repositories on a weekly basis?
Apart from loading their individual GitHub profiles and comparing the statistics?
My team is growing at quite a rapid pace, and soon it will be difficult to find the time to manually compare them. We also work in 4 different times zones thus it can be difficult to sync up with everyone effectively.
The current main view which offer user activity comparison is the Graphs view:
(That and the Pulse view)

Review GitHub own activity for extended period

I would like to review my GitHub activities for the past 12 months. On my public profile I can see as much as one month only. I can go to an individual repository and review all the commits for any period of time, of course, but this becomes unfeasible when I have to interleave data from dozens of repositories.
Is there an advanced query or page that allows me to see or download this aggregated data?
Looks like GitHub does not allow viewing contribution data for more than a Month by default but if you use it's apis you can build something that can keep track of your contribution for how ever long you want it to.
Here's where GitHub talks about contribution.
https://help.github.com/articles/viewing-contributions-on-your-profile-page/

Working with boards in Phabricator

I think this question belongs here (but it is may get voted down). My company is migrating from GitHub to Phabricator. But, not sure how to implement the "boards" feature. I've never worked on a team that used kanban. We have created 8 different "projects" in Phabricator, but we are too small to have separate teams for each project. There are 4 columns for each board:
backlog
selected
in progress
done
How do people get 1 board for doing planning across projects. The only thing I can think of is to create a "master" project that every task gets added to in addition to it's "real" project. For example, an task might be:
Allow support user to resent password reset email
And it would get tagged with the projects "master" and "support_app".
Is there a better way of doing this?
You can plan an release and add milestones for product level and add multiple projects in it and spread it across team members in multiple projects in further small tasks.
Then you will have an individual task board for each team on team level tasks.
A team member then exist across multiple projects and you can also view , how an person is loaded across multiple projects.
If you want to look at bigger picture then you can see the milestones/release level status.

TFS - Good practice - more users at one station

We have one perplexity about current situation with TFS. There are 3 branches: Develop, Main, Production. Also, we have separate station where we are doing versions build and at that station is mapped Main and Production branch. At stations of our programmers are mapped Develop and Main branches and we are doing Merge between these two branches at our local stations, while Merge between Main and Production doing at separate station for versions build.
We have issue because until now, merge at production station were doing with only one shared user and we don't have information which programmer done that work for specific version (we can see merge at Main branch in that period, but we need more accurate information). One solution could be that we do merge at production at our local stations. Other solution can be that each user has own folders at production stations, but we would like to consider is it possible to use same folders at production station for all users??? Now, we get message that folders are already used from other user at same Workspace. Is something like that possible? Do you have suggestions what are good practices in this situation?
This blog post from Grant Holliday seems to provide information on the standard capability of TFS2010 to service Public Workspaces: http://blogs.msdn.com/b/granth/archive/2009/11/08/tfs2010-public-workspaces.aspx:
The Public Workspaces feature removes this limitation of one user per
workspace and allows multiple users to use the same workspace mappings
on a single machine. Unlocked workspaces are sometimes also referred
to as "Shared workspaces", as they can be shared among multiple
people.