Rebalance exobots: make them bad at everything but let them live anyw…

.appveyor.yml

@@ -0,0 +1,54 @@
+os: Visual Studio 2017
+
+version: ci-{build}
+
+environment:
+  matrix:
+    - BUILD_SYSTEM: CMAKE
+    - BUILD_SYSTEM: MSVC
+
+matrix:
+  allow_failures:
+    - BUILD_SYSTEM: CMAKE
+
+init:
+  - git config --global core.eol native
+  - git config --global core.autocrlf true
+
+clone_depth: 50
+
+skip_commits:
+  files:
+      - default/
+      - '**/*.md'
+      - '**/*.xml'
+      - '**/COPYING'
+  message: /.*\[(skip appveyor)|(appveyor skip)\].*/
+
+install:
+  - cd ..
+  - ps: Start-FileDownload https://github.com/freeorion/freeorion-sdk/releases/download/v11/FreeOrionSDK_11_MSVC-v141-Win32.zip -FileName FreeOrionSDK.zip
+  - unzip -q FreeOrionSDK.zip
+  - cp bin/* freeorion/
+  - cd freeorion
+
+before_build:
+  - if "%BUILD_SYSTEM%" == "MSVC" (
+      cd msvc2017
+    )
+  - if "%BUILD_SYSTEM%" == "CMAKE" (
+      mkdir build
+    )
+
+build_script:
+  - if "%BUILD_SYSTEM%" == "MSVC" (
+      msbuild FreeOrion.sln /maxcpucount /property:BuildInParallel=true /property:CL_MPCount=2 /property:PlatformToolset=v141 /property:Configuration=Release /logger:"C:\Program Files\AppVeyor\BuildAgent\Appveyor.MSBuildLogger.dll" /verbosity:minimal
+    )
+  - if "%BUILD_SYSTEM%" == "CMAKE" (
+      pushd build &&
+      cmake -G "Visual Studio 15 2017" -T v141 -A Win32 -DBUILD_TESTING=On .. &&
+      cmake --build . --config "Release" -- /maxcpucount /property:BuildInParallel=true /property:CL_MPCount=2 /logger:"C:\Program Files\AppVeyor\BuildAgent\Appveyor.MSBuildLogger.dll" /verbosity:minimal &&
+      popd
+    )
+
+test: off

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# Code owners for translation stringtables
+ru.txt @Cjkjvfnby @o01eg

.github/ISSUE_TEMPLATE.md → .github/ISSUE_TEMPLATE/bug.md

@@ -1,24 +1,30 @@
+---
+name: Report bug
+about: Report problems and bugs with FreeOrion.
+labels: "category:bug"
+---
+Bug Report
+==========
 <!--
-Please fill in a a meaningful and concise issue title in the title field above.
+Please fill in a a meaningful and concise title in the field above.
 It helps us to classify the issue even  before reading the body and handling the
-issue a bit better.  Prefix the title with labels you find appropriate to
-describe the issue like "[Bug]" in case of a bug, "[Feature]" for a feature
-request.
+issue a bit better.
 
 Examples:
-  * Great: "[Bug] Unable to select fleet in galaxy map"
-  * Good: "[Bug] Unable to click fleet"
+  * Great: "Unable to select fleet in galaxy map"
+  * Good: "Unable to click fleet"
   * Not really okay: "Issue with fleets"
   * Horrible: "HELP!!!"
 -->
 
 
-### Environment
+Environment
+-----------
 <!--
 You don't need to provide the information in section when they are not useful in
-the context of this issue.  For example feature requests may not need a
-FreeOrion version, but maybe depend on the operating system you use.  When in
-doubt provide all information you have available.
+the context of this issue.  For example a crashing hosted server may not need
+information about the graphic card, but maybe depend on the operating system you
+use.  When in doubt provide all information you have available.
 
 You can find the FreeOrion version number in the lower right corner of the game
 main screen.
@@ -37,10 +43,10 @@ so, `Windows 8 Pro` instead of `Windows` or `Mac OSX Mountain Lion` instead of
   * Compiled from source
 
 
-### Description
+Description
+-----------
 <!--
-Add a meaningful description of the bug you encountered or of the feature you
-want to request.
+Add a meaningful description of the bug you encountered.
 
 If a screenshot or image helps to describe the issue content feel free to create
 one.
@@ -53,22 +59,22 @@ found on
 -->
 
 
-### Expected Result
+Expected Result
+---------------
 <!--
-If this issue is not a bug you can remove this section.
-
 When you enter an issue please add a description of what behaviour you would
 expect from the game instead of the issue.
 -->
 
 
-### Steps to reproduce
+Steps to reproduce
+------------------
 <!--
-If this issue is not a bug you can remove this section.
-
 If the error only manifests itself after doing a certain number of actions
 please add a list of steps to reproduce the bug.  If the error only occurs in
 a certain game state please be sure to add a save game to the issue.
+
+To upload save games please pack them into a Zip archive (*.zip) first.
 -->
 * First step.
 * Second step.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,4 @@
+contact_links:
+  - name: FreeOrion Forum
+    url: https://freeorion.org/forum/
+    about: Get in touch with the FreeOrion developers and community for gameplay support

.github/ISSUE_TEMPLATE/feature.md

@@ -0,0 +1,31 @@
+---
+name: Feature request
+about: Propose a new or improved functionality to FreeOrion.
+labels: "category:feature"
+---
+Feature request
+===============
+
+Idea
+----
+<!--
+Write down a short explanation of what the new feature consists of.  What
+should be added or changed to the project?
+-->
+
+
+Gain
+----
+<!--
+Explain why the introduction of this feature would improve the project.
+-->
+
+
+Discussion
+----------
+
+<!--
+Please create a new forum thread for discussions and link it here;
+to directly open the the "New Topic" form you can use the link below:
+https://www.freeorion.org/forum/posting.php?mode=post&f=6
+-->

.github/RELEASE_TEMPLATE.md → .github/ISSUE_TEMPLATE/release.md

@@ -1,6 +1,12 @@
+---
+name: Publish release
+about: "Team only: Create a tracking issue for a FreeOrion release."
+title: Release X.Y.Z preparation
+assignees: Vezzra
+---
 <!--
-Please  use the issue title 'Release X.Y.Z preparation' and replace X, Y and Z
-with the major, minor and patch release version number.
+Please replace X, Y and Z with the major, minor and patch release version
+number in the title above.
 
 The X.Y.Z convention as placeholder for the actual version number is used
 thoughout this document.
@@ -51,7 +57,7 @@ git checkout -b release-vX.Y.Z master
 ```
 * [ ] *On release branch HEAD* - Update version number in `CMakeLists.txt` and
       `cmake/make_versioncpp.py` to `vX.Y.Z`, remove trailing `+` if needed.
-* [ ] *On release branch HEAD* - Remove `Super Testers` species.
+* [ ] *On release branch HEAD* - Disable `Super Testers` species by default.
 * [ ] *On master branch HEAD* - Update version number in `CMakeLists.txt` and
       `cmake/make_versioncpp.py` to `vX.Y.Z+`.
 * [ ] Push updated release and master branch to GitHub.

.github/labels.md

@@ -26,7 +26,7 @@ rule of thumb there is at least one label from every category that needs to be
 applied to an issue but use common sense to check if the label is appropriate or
 not for the specific Issue/PR.
 
-Currently there are three categories:
+Currently there are four categories:
 
 
 #### Label category `category`
@@ -42,6 +42,15 @@ affected by.  This should help developers to identify if they have required
 knowledge or interests to handle the issue.  There should be at least one
 component listed for an Issue.
 
+#### Label category `priority`
+
+The priority labels help developers and contributors to prioritize the Issue/PR,
+to focus their efforts more efficiently. There are only two `priority:*` labels,
+for high and low priority. Assigning no `priority:*` label means the Issue/PR
+has "standard"/"normal"/"medium" priority, which is the default (and should
+apply to the majority of issues/PRs). Priority may change over the lifetime of
+the Issue/PR.
+
 #### Label category `status`
 
 With the status category developers, managers or issue reporters can check if
@@ -112,7 +121,16 @@ content of the PR may require extensive gameplay balance testing.
 
 The Issue/PR deals with non-game related infrastructure that aids development.
 For example this includes issues with the project homepage, used external
-services like continuous integration or hosting of release binaries.
+services like continuous integration, hosting of release binaries, tools for
+checking code style, etc.
+
+Infrastructure Issues/PRs should not entail/contain any changes to the actual
+codebase unless such changes are essentially required by the Issue/PR and would
+not make sense outside of its context. Any such non-codebase Infrastructure
+Issues/PRs should not be assigned a milestone unless they have particular
+relevance to the milestone, such as by establishing some type of
+testing/verification of the codebase which is desired to be completed for the
+milestone. 
 
 #### Label `component:internal`
 
@@ -149,6 +167,28 @@ should be used in conjunction with `component:art music text assets`; when this
 Issue addresses external documentation like the FO wiki add the
 `component:infrastructure` label.
 
+#### Label `priority:high`
+
+The Issue/PR is very urgent or important and should be addressed/finished as
+soon as possible, and developers/contributors should focus their efforts on them
+before other things. Usually applied to critical bugs and features relevant for
+upcoming releases.
+
+#### Label `priority:low`
+
+The Issue/PR is of minor importance/urgency and can be set aside for more
+important or urgent things. Usually applied to e.g. nice-to-have features or
+bugs that are more of cosmetic nature or a minor annoyance than something that
+impedes or breaks gameplay.
+
+#### Label `status:abandoned`
+
+The contributor providing the PR has stopped working on it and either explicitely
+stated that they have no intentions or cannot be expected to resume their work
+(e.g. because they left the project with no intentions of coming back). Also, no
+one is going to pick up the PR for them, so it can be sufficiently safely assumed
+that the PR will never be finished.
+
 #### Label `status:cherry-pick for release`
 
 The PR should be applied to the currently open release branch.  Use this label
@@ -163,7 +203,7 @@ the number of the covering Issue/PR in a comment and close this Issue/PR.  For
 PRs document why the other PR was chosen over this PR.  For Issues copy over
 new knowledge that is valuable to solve the covering Issue.
 
-#### Label `status:follow up`
+#### Label `status:superseded`
 
 The PR discussion showed that the proposed implementation is insufficient in
 some way or the PR in itself is malformed.  Usually not required as we prefer

.gitignore

@@ -57,16 +57,11 @@ DerivedData
 # FreeOrion specific
 *.zip
 /util/Version.cpp
-/Installer/FreeOrion_Install_Script.nsi
+/packaging/windows_installer.nsi
+/packaging/Info.plist
 /doc/apidoc-commit-message
 
-# FreeOrion Xcode project
-/Xcode/dep/
-/Xcode/build/
-/Xcode/Info.plist
-contents.xcworkspacedata
-
-# FreeOrion MSVC2010 project
+# FreeOrion MSVC project
 *.pdb
 *.log
 *.tlog
@@ -81,6 +76,26 @@ contents.xcworkspacedata
 *.opensdf
 *.res
 
+# Incremental build files
+*.ipdb
+*.ilk
+*.iobj
+
 # KDevelop4
 *.kdev4
 *.db
+
+# git mergetool
+*.orig
+
+# vim
+.*.sw?
+
+
+# Visual Studio
+.vs/
+.vscode/
+
+# linters temp files
+.mypy_cache/
+.pytest_cache/