Sebastian Oliva
14 years ago
Hi!, I got an e-mail on a survey about Git, so any comments on our
work-flow would be nice.
-------- Original Message --------
Subject: Re: Git survey
Date: Tue, 24 May 2011 10:48:28 -0700
From: Scott Chacon <schacon-***@public.gmane.org>
To: Sebastian Oliva <tian2992-***@public.gmane.org>
I'm trying to get a better idea of how people use Git and
GitHub within commercial organizations for a book I'm working on for
O'Reilly. The book (should I finish it) will be CC-licensed and
freely available online. My goal with these interviews is to aggregate
best-practices for different org and team sizes so teams new to Git
and GitHub can pick and choose from common and tested patterns.
So, that said, here are the questions I would like to know:
1. Where do you work, and what is your overall company size?
2. What is the makeup of your development team? How many people work
on your projects (developers, designers, others) and how is the team
structured?
3. How long have you been using Git and what did you switch from (if
anything)? Do you still use other VCS systems in your organization?
What made you switch?
4. Are there any common development methodologies followed? (Agile,
SCRUM, etc)
5. What are the physical location of team members? Are they all in
one office or distributed in different locations and timezones?
6. What is your overall development cycle? Walk me step by step
through creating and deploying a new feature or fixing a reported bug,
including command line invocations if possible. Some things I would
really like to know would be:
- how do you host your git repositories?
- how many repositories do you work on and how are they arranged?
- what is your branching policy? do you have any long-lived branches
with specific meanings? do you have a naming policy?
- is there a difference between how you approach large features that
may take months to accomplish?
- is there any review process? if so, how do you accomplish that?
- what is your deployment method and frequency?
- are there any permissions or acls in place? how are they enforced?
- is there any ticketing system integration? how do you know what to
work on next or status of existing issues?
- are there build systems or any other system coupled to or triggered
from your version control? documentation builds, notifications, etc.
- do you use any helping scripts or wrappers? if so, how do you
distribute them to your team members?
- do you have any training procedures in place for new hires? how do
they get familiar with your workflow and policies?
- do you have a tagging policy?
7. What issues do your developers new to Git tend to have the most?
8. Do you have sub-projects (libraries or shared code kept as a
separate repository inside your main repository)? If so, how do you
handle them? Submodules?
9. Are there any tools used, such as IDEs with Git integration, GUIs
or libraries that interface with Git?
10. What is the Open Source policy at your company? Do you host or
work on OS projects? Are they used in your commercial product?
11. Are there any changes in your workflow practices since you first
adopted Git? ie: is there something you tried doing using Git that you
have since changed or abandoned because it didn't work well?
12. What are the differences in your workflow from your previous VCS
solution?
13. What are your remaining pain points in using Git? What could be
better or easier?
14. Is it OK to quote you and/or name your company? If not, the
information will be presented anonymously.
15. Would you be interested in doing a longer, more official interview
for the purposes of publishing a white paper?
I realize that is a lot - any information you can provide and insight
you have on lessons learned would be helpful to me. Answer whatever
you can. The next time I'm in your neck of the woods, make sure I buy
you a beer.
Thanks again,
Scott
work-flow would be nice.
-------- Original Message --------
Subject: Re: Git survey
Date: Tue, 24 May 2011 10:48:28 -0700
From: Scott Chacon <schacon-***@public.gmane.org>
To: Sebastian Oliva <tian2992-***@public.gmane.org>
I'm trying to get a better idea of how people use Git and
GitHub within commercial organizations for a book I'm working on for
O'Reilly. The book (should I finish it) will be CC-licensed and
freely available online. My goal with these interviews is to aggregate
best-practices for different org and team sizes so teams new to Git
and GitHub can pick and choose from common and tested patterns.
So, that said, here are the questions I would like to know:
1. Where do you work, and what is your overall company size?
2. What is the makeup of your development team? How many people work
on your projects (developers, designers, others) and how is the team
structured?
3. How long have you been using Git and what did you switch from (if
anything)? Do you still use other VCS systems in your organization?
What made you switch?
4. Are there any common development methodologies followed? (Agile,
SCRUM, etc)
5. What are the physical location of team members? Are they all in
one office or distributed in different locations and timezones?
6. What is your overall development cycle? Walk me step by step
through creating and deploying a new feature or fixing a reported bug,
including command line invocations if possible. Some things I would
really like to know would be:
- how do you host your git repositories?
- how many repositories do you work on and how are they arranged?
- what is your branching policy? do you have any long-lived branches
with specific meanings? do you have a naming policy?
- is there a difference between how you approach large features that
may take months to accomplish?
- is there any review process? if so, how do you accomplish that?
- what is your deployment method and frequency?
- are there any permissions or acls in place? how are they enforced?
- is there any ticketing system integration? how do you know what to
work on next or status of existing issues?
- are there build systems or any other system coupled to or triggered
from your version control? documentation builds, notifications, etc.
- do you use any helping scripts or wrappers? if so, how do you
distribute them to your team members?
- do you have any training procedures in place for new hires? how do
they get familiar with your workflow and policies?
- do you have a tagging policy?
7. What issues do your developers new to Git tend to have the most?
8. Do you have sub-projects (libraries or shared code kept as a
separate repository inside your main repository)? If so, how do you
handle them? Submodules?
9. Are there any tools used, such as IDEs with Git integration, GUIs
or libraries that interface with Git?
10. What is the Open Source policy at your company? Do you host or
work on OS projects? Are they used in your commercial product?
11. Are there any changes in your workflow practices since you first
adopted Git? ie: is there something you tried doing using Git that you
have since changed or abandoned because it didn't work well?
12. What are the differences in your workflow from your previous VCS
solution?
13. What are your remaining pain points in using Git? What could be
better or easier?
14. Is it OK to quote you and/or name your company? If not, the
information will be presented anonymously.
15. Would you be interested in doing a longer, more official interview
for the purposes of publishing a white paper?
I realize that is a lot - any information you can provide and insight
you have on lessons learned would be helpful to me. Answer whatever
you can. The next time I'm in your neck of the woods, make sure I buy
you a beer.
Thanks again,
Scott