Developer_Guide

Useful Links

• https://help.github.com/articles/fork-a-repo/

IRC Details

• Web client can be found on the Afternet website
• Channels #DUWS-R and #DUWS-R-Devs

Quick Setup

NOTE: All commands here assume you are using "Git Bash" to input them. The general process will be the same for using tools other than "Git Bash" but specifics may be different.

• Fork the project here
• Clone the project to your computer
• Add the DUWS-R-Team project as a remote named "upstream'
  • git remote add upstream git@github.com:DUWS-R-Team/DUWS-R.git

General Guidelines

• You should perform your work in a branch that was created from master
  • You can do this by running git checkout master then git checkout -b (yourBranchName)
• All contributions to DUWS-R will go through Pull Requests.
  • These pull requests allow the rest of the team to review the work and provide feed back such as better ways to accomplish the same thing or possible bugs.
• Please configure your environment not to use tab characters.
  • This allows the code to be read easily from the github web GUI. Also, individual members should not have to configure their tab stop when moving their development tools between multiple projects.
  • DUWS-R-Team has standardized on 4 spaces for each indention in code.
• Please refrain from placing your name in the source code.
  • The DUWS-R-Team members feel that the code for the project is not "owned" by one member or another. The group as a whole is responsible for all bugs as well as all features. Git supports, via blame, seeing the last member that "touched" a line of code as well as all contributors to the project as a whole.

Using deployLocalBuild.ps1

• Create a file named localDevDeploy.properties
• Model the contents of the file as below

arma3Install=D:\Program Files (x86)\Steam\steamapps\common\Arma 3
pboManagerInstall=C:\Program Files\PBO Manager v.1.4 beta