The figure below shows a proposed configuration for using Git repositories to share code between CHILL and S-Pol. Each group has its own code repository that contains the "official" version of source code (and documents) for their own radar. Note that Git works much differently that CVS or Subversion. A developer using CVS or Subversion checks out a "working copy" from the central repository. To commit any changes, a developer commits against the central repository. In contrast, when you develop using Git, you "clone" a complete repository, and can commit changes against your own repository. Once you are ready for other developers to use your changes, you "push" change sets to a group repository. At regular intervals, each group would "pull" changes from each others "official" repository, to share bug fixes or enhancements. Although Git provides excellent merging tools, we will still want to coordinate between individual developers and between our two groups, since we want to avoid both groups simultaneously making large changes to the same files. (This is no different than with CVS or Subversion).
Note that S-Pol developers may sometimes use an additional repository, particularly when S-Pol is in the field, and may not have access to the EOL Git repository.
