just forgot to add. as eric mentions, it would be
helpful to have a public and acknowledged list of
companies who use svn. that is one of the things
he uses against the change. this would be a
major motivation to convince the (dilbert principle)
guy who takes this kind of decisions without
having an idea, and that relies mainly on what
is mainstream and what is not.
on that behalf, i said that most major companies
do. by monitoring the email addresses of posters
to this list you get an idea. i mentioned on my
proposal that google is partially sponsoring
svn development (besides using it).
perhaps, it would be easier to list companies
who still don't use svn ...
2007/2/6, marc gonzalez-carnicer <carnicer.lists@gmail.com>:
> i have a guy in my company who behaves a little bit
> like Eric's fellow. Fortunately, svn migration is on the
> way because this guy has nothing to say about this,
> I went directly to management with a well written
> proposal, with the motivations to switch to svn.
>
> The guy's points for not dropping VSS were :
>
> * VSS is simple to use, he learned to use it in 15'
> * VSS is "wonderfully" integrated into MS dev tools
> * there is no need to change
> * VSS'2005 (6?) has all the features of svn -- ;)
>
> his points are easily refuted, but still he does
> not want to admit he is wrong. what is amazing
> is how some people get lost outside of MS's
> prison.
>
> i have to admit that changing from VSS to svn
> requires (for the basic user) to learn how to
> resolve conflicts, and to watch out for the
> outcome of automated merges.
>
> my advice is to ignore that guy and send your
> proposal to the decision takers. i had to do it
> because he was getting noisy. i was also
> lucky that the decision taker (who did not know
> much about vss nor svn) was adviced by
> his trusted project manager, who also wanted
> to work with svn but had had not time to try it.
>
> regards,
>
>
> /marc
>
>
>
>
> 2007/2/6, Janine Sisk <janine@furfly.net>:
> > On Feb 5, 2007, at 12:34 PM, L. Wayne Johnson wrote:
> >
> > > The bottom line is Visual Source Safe is *not* *safe*. I have used
> > > it at
> > > another company and we had nothing but problems with it.
> >
> > It was a long time ago now, but the company I worked for converted
> > from CVS to VSS and there were certain files which were corrupted
> > every time you checked them in. Same corruption every time, same
> > files. No-one at Microsoft seemed to be too concerned, nor did any
> > of the people responsible for the change choose to act like it
> > mattered. I no longer remember how it was resolved; I think I may
> > have left the company while it was still going on.
> >
> > Each time I read Eric's posts about this guy I wonder "where is his
> > manager?". Unless he is single-handedly responsible for some big
> > chunk of the company's bottom line, he should not be allowed to
> > behave like this. Have you made sure that his boss, and yours, are
> > aware of his obstructionist ways?
> >
> > janine
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: users-help@subversion.tigris.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 6 11:28:26 2007