diff options
| -rw-r--r-- | paper.tex | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -662,11 +662,11 @@ Modern version control systems provide many more capabilities that can be levera \subsection{Multi-user collaboration on single build directory} \label{sec:collaborating} -Because the project's source and build directories are separate, it is possible for different users to share a build directory, while working on their own separate project branches during a collaboration. -Similar to the parallel branch that is later merged in Figure \ref{fig:branching}(a). -To enable this mode, \inlinecode{./project} script has a special \inlinecode{--group} option which takes the name of a (POSIX) user group in the host OS. +Because the project's source and build directories are separate, an option is provided for different users to share a build directory, while working on their own separate project branches during a collaboration. +This is similar to the parallel branch that is later merged in Figure \ref{fig:branching}(a). +To enable this mode, the \inlinecode{./project} script has an option \inlinecode{--group} that must be given the name of a (POSIX) user group in the host OS. All files built in the build directory are then automatically assigned to this user group, with read and write permissions. -Of course, avoiding conflicts in the build directory, while members are working on different branches is up to the team. +Permission management and avoiding conflicts in the build directory while members work on different branches is the responsibility of the team. \subsection{Publishing the project} \label{sec:publishing} |