If it is their first time using source control, starting them with DVCS might save them the "unlearning" that others are having to do!
On 2011-11-01, at 11:16 PM, Adron Hall <[email protected]> wrote: Do they have stuff beyond just the code and general web assets? In other words, are their any others such as graphic artists, documentation people, or such that want to keep a "backup" of their work? If so, that may be a consideration too. If it is all static content, text based, I think whatever would be the easiest to teach them to use would be the best option. If they're GUI oriented, Tortoise + Subversion would probably be ok. If they're a bit more advanced and especially if they do any remote work, I'd push for some distributed control, i.e. good ole' Git or Mercurial. Just my 2 cents. Other than that, if these seem like a bit much, I say just stick multiple copies in Dropbox and call it a day. :) -Adron On Tue, Nov 1, 2011 at 8:10 PM, Stevi Deter <[email protected]> wrote: > I know it's not what all the cool kids are using these days, but I've had > excellent success using SVN in similar situations. > > Heck, I've even managed to get database devs to check their code into SVN. > > -Stevi > > > > On Tuesday, November 1, 2011, Jeff Schumacher <[email protected]> > wrote: > > So imagine there is a team that has an old sckool setup, where there are > multiple developers working on the same copy of source code that exists out > on a network share. Also say that this application could be ASP.NET, > Classic ASP, or even PHP. The company only has 3 developers, and they > rarely run into either other. One person is responsible for rebuilding the > application, and this practice has been working for this team for years. > They get stuff accomplished, and that is key. They do not run local copies > of the application due to various reasons (this is not the point I'm trying > to argue, as I don't agree with this setup). This team also learned a long > time ago that backups are critical, so they have an automated system on > this network share that detects file changes and makes a archived, > timestamped, copy of the time. It's basically a rudimentary source control > system. > > > > Now, this team knows that they need to get with the times and use a > proper SCM, and they would also like to link their commits with their bug > tracking system, which happens to be Jira. So the question is, what SCM do > you think would work in their current shared source base setup, and why? I > have my opinion on which SCM I think might work, but rather than taint > suggestions, I'll leave my opinion out for the moment. > > > > > > Jeff > > > > -- > > You received this message because you are subscribed to the Google > Groups "Seattle area Alt.Net" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > [email protected]. > > For more options, visit this group at > http://groups.google.com/group/altnetseattle?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Seattle area Alt.Net" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/altnetseattle?hl=en. > -- *Adron B Hall* *Tech*: http://compositecode.com *Transit*: http://transitsleuth.com *Twitter*: http://www.twitter.com/adron -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en. -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en.
