Shared access to schematic/project

On 9/2/2011 12:41 AM, Steve Klett wrote:

Hi,

 

I have hired a contractor to do some eagle work for me as I'm not yet up to speed enough to meet a deadline.  Anyway, so I'd still like to help and be involved in the process but I don't see how the two of us can work on the same file without creating a real mess.  I can solve the shared access issue by granting him VPN to our file server, but I highly doubt that eagle will be too happy if we both are editing the file at the same time.  THe only option I can think of is to use version control or a basic "Are you working right now?  No? OK, then I will for awhile and will email you when I'm done" type approach.

 

Anyone here who works or has worked in a multiuser scenario have any tips for me?

 

Thanks for reading,

Steve

 

Hi Steve,

To clarify, the XML file format will be implemented in Version 6 so from

that point on version control systems will be very easily able to handle

our files.

There are many possible choices, I personally like Bazaar since it has a

very smooth GUI interface, however there are many other alternatives

such as RCS, CVS, Mercurial, SVN, Git, etc.

I will second the opinion of the other posters who have stated that it's

best to let the contractor do most of the work and just periodically

look over the work and make comments. The mental picture Andrew

mentioned is a very real thing, and oversights can definitely occur if

two people start making changes at the same time.

What I've seen work well is to set milestones. When the contractor

reaches the milestone have him send you the files, you look them over

and comment. Once everything is approved he continues to work on to the

next milestone and the process repeats.

In this way designs errors can be nipped in the bud.

hth,

Jorge Garcia

On 9/2/2011 12:41 AM, Steve Klett wrote:

Hi,

 

I have hired a contractor to do some eagle work for me as I'm not yet up to speed enough to meet a deadline.  Anyway, so I'd still like to help and be involved in the process but I don't see how the two of us can work on the same file without creating a real mess.  I can solve the shared access issue by granting him VPN to our file server, but I highly doubt that eagle will be too happy if we both are editing the file at the same time.  THe only option I can think of is to use version control or a basic "Are you working right now?  No? OK, then I will for awhile and will email you when I'm done" type approach.

 

Anyone here who works or has worked in a multiuser scenario have any tips for me?

 

Thanks for reading,

Steve

 

Hi Steve,

To clarify, the XML file format will be implemented in Version 6 so from

that point on version control systems will be very easily able to handle

our files.

There are many possible choices, I personally like Bazaar since it has a

very smooth GUI interface, however there are many other alternatives

such as RCS, CVS, Mercurial, SVN, Git, etc.

I will second the opinion of the other posters who have stated that it's

best to let the contractor do most of the work and just periodically

look over the work and make comments. The mental picture Andrew

mentioned is a very real thing, and oversights can definitely occur if

two people start making changes at the same time.

What I've seen work well is to set milestones. When the contractor

reaches the milestone have him send you the files, you look them over

and comment. Once everything is approved he continues to work on to the

next milestone and the process repeats.

In this way designs errors can be nipped in the bud.

hth,

Jorge Garcia

On Fri, 2 Sep 2011, Jorge Garcia wrote to us saying :

>To clarify, the XML file format will be implemented in Version 6 so

>from that point on version control systems will be very easily able to

>handle our files.

I think it needs to be pointed out that merely being a text file does

NOT mean version control systems will "be able to handle" the files any

better.

All version control systems can "handle" binary files to the extent of

storing them. The extra features they can provide for text files are

diff and merge methods. However, these functions are universally

implemented on a line-by-line basis, such that the tool can identify

lines that have been added, deleted, moved etc. For most programming

languages, this line-by-line approach works well. For XML it absolutely

does not. The thing is, XML is fundamentally not line-based - it's

simply a token stream where the tokens are in ASCII rather than binary.

--

Rob Pearce                       http://www.bdt-home.demon.co.uk

The contents of     | All power corrupts, but we need electricity.

this message are    |

purely my opinion.  |

Don't believe a     |

word.               |