Merge pull request #1 from googleforgames/master

Merge to update to current

Author: syntxerror

Makefile

@@ -24,7 +24,7 @@
 # If you want information on how to edit this file checkout,
 # http://makefiletutorial.com/
 
-BASE_VERSION = 0.0.0-dev
+BASE_VERSION = 1.0.0
 SHORT_SHA = $(shell git rev-parse --short=7 HEAD | tr -d [:punct:])
 VERSION_SUFFIX = $(SHORT_SHA)
 BRANCH_NAME = $(shell git rev-parse --abbrev-ref HEAD | tr -d [:punct:])

cloudbuild.yaml

@@ -113,7 +113,7 @@ steps:
     path: '/go'
 
 substitutions:
-    _OM_VERSION: "0.0.0-dev"
+    _OM_VERSION: "1.0.0"
     _GCB_POST_SUBMIT: "0"
     _GCB_LATEST_VERSION: "undefined"
 logsBucket: 'gs://open-match-site-build-logs/'

site/config.toml

@@ -7,7 +7,7 @@ enableRobotsTXT = true
 theme = ["docsy"]
 
 # Will give values to .Lastmod etc.
-#enableGitInfo = true
+# enableGitInfo = true
 
 # Language settings
 contentDir = "content/en"
@@ -74,7 +74,7 @@ github_docs_repo = "https://github.com/googleforgames/open-match-docs"
 gcs_engine_id = "008748710159674449076:sqoelpnrdoe"
 
 release_branch = "master"
-release_version = "0.0.0-dev"
+release_version = "1.0.0"
 slack_link = "https://join.slack.com/t/open-match/shared_invite/enQtNDM1NjcxNTY4MTgzLTM5ZWQxNjc1YWI3MzJmN2RiMWJmYWI0ZjFiNzNkZmNkMWQ3YWU5OGVkNzA5Yzc4OGVkOGU5MTc0OTA5ZTA5NDU"
 
 # User interface configuration
@@ -112,3 +112,9 @@ no = 'Sorry to hear that. Please <a href="https://github.com/googleforgames/open
 	url = "https://github.com/googleforgames/open-match"
 	icon = "fab fa-github"
         desc = "Source Code"
+
+[frontmatter]
+date = ["date", "publishDate", "lastmod"]
+lastmod = [":fileModTime"]
+publishDate = ["publishDate", "date"]
+expiryDate = ["expiryDate"]

site/content/en/_index.html

@@ -44,7 +44,17 @@
 {{< /blocks/section >}}
 
 
-{{< blocks/section color="primary"  >}}
+{{< blocks/section color="primary" >}}
+<div class="col">
+		<h2 class="text-center pb-3">Companies using Open Match</h2>
+		<p class="text-center showcase">
+			<a href="http://unity.com/"><img alt="unity" width="150" src="images/unity.png" /></a>
+		</p>
+</div>
+{{< /blocks/section >}}
+
+
+{{< blocks/section color="secondary"  >}}
 
 {{% blocks/feature icon="fab fa-slack" title="Join us on Slack" url="https://join.slack.com/t/open-match/shared_invite/enQtNDM1NjcxNTY4MTgzLTM5ZWQxNjc1YWI3MzJmN2RiMWJmYWI0ZjFiNzNkZmNkMWQ3YWU5OGVkNzA5Yzc4OGVkOGU5MTc0OTA5ZTA5NDU" url_text="Join us" %}}
 Join the community on Slack

site/content/en/docs/Contribute/_index.md

@@ -13,7 +13,7 @@ If there's something you see that can be [improved](https://github.com/googlefor
 
 There are many ways to get in touch with the Open Match community.
 
-* [Slack](https://open-match.slack.com/) ([Join](https://join.slack.com/t/open-match/shared_invite/enQtNDM1NjcxNTY4MTgzLWQzMzE1MGY5YmYyYWY3ZjE2MjNjZTdmYmQ1ZTQzMmNiNGViYmQyN2M4ZmVkMDY2YzZlOTUwMTYwMzI1Y2I2MjU)) - Talk to the Open Match engineers and users on Slack.
+* [Slack](https://open-match.slack.com/) ([Join](https://open-match.slack.com/join/shared_invite/zt-5k57lph3-Oe0WdatzL32xv6tPG3PfzQ#/)) - Talk to the Open Match engineers and users on Slack.
 * [open-match-discuss@ mailing list](https://groups.google.com/forum/#!forum/open-match-discuss) - Get the latest information on changes happening to Open Match.
 
 ## Code of Conduct

site/content/en/docs/Guides/access.md renamed to site/content/en/docs/Guides/Access/_index.md

@@ -1,6 +1,6 @@
 ---
-title: "Customize core Open Match"
-linkTitle: "Customize core Open Match"
+title: "Customize Core Open Match"
+linkTitle: "Customize Core Open Match"
 weight: 5
 description: >
   This guide covers how to customize your Open Match deployment.
@@ -38,7 +38,7 @@ To configure Open Match with your custom config, create a new YAML file with thi
 kubectl apply -f <filename_here>
 ```
 
-The [Evaluator Guide]({{< relref "../Guides/evaluator.md" >}}) gives an overview of Synchronization, Evaluation and all the related configuration.
+The [Evaluator Guide]({{< relref "../Evaluator/_index.md" >}}) gives an overview of Synchronization, Evaluation and all the related configuration.
 
 ## Configurations
 The following tables lists the configurable parameters of the Open Match override configmap and their default values.

site/content/en/docs/Guides/api.md renamed to site/content/en/docs/Guides/Api/_index.md

@@ -51,8 +51,8 @@ To allow generation of proposals using overlapping Tickets but still provide uni
 Open Match provides a default score based Evaluator that can be used in most common scenarios but it also provides the user the ability to build your own Evaluator and to customize Open Match to use the user's Evaluator. At a high level, there are three evaluation scenarios for you to consider when using Open Match:
 
 1. Your MatchProfiles completely partition the Ticket Pool and so you will never have collisions. The default Evaluator handles this scenario and you do not have to make any changes.
-2. Your MatchProfiles may use overlapping Ticket Pools - but each MatchFunction can simply generate a quality score for that Match based on certain game specific criteria (latency, mmr etc.). The default Evaluator can be used for this scenario. See [Default Evaluator Tutorial]({{< relref "../Tutorials/DefaultEvaluator/_index.md" >}})
-3. You have complex evaluation logic that cannot be simplified to a score for a Match but rather involves actually comparing some details of the overlapping Matches. Open Match provides you with the ability to plug in your custom Evaluator to handle this case. See the [Custom Evaluator Tutorial]({{< relref "../Tutorials/CustomEvaluator/_index.md" >}}) for details.
+2. Your MatchProfiles may use overlapping Ticket Pools - but each MatchFunction can simply generate a quality score for that Match based on certain game specific criteria (latency, mmr etc.). The default Evaluator can be used for this scenario. See [Default Evaluator Tutorial]({{< relref "../../Tutorials/DefaultEvaluator/_index.md" >}})
+3. You have complex evaluation logic that cannot be simplified to a score for a Match but rather involves actually comparing some details of the overlapping Matches. Open Match provides you with the ability to plug in your custom Evaluator to handle this case. See the [Custom Evaluator Tutorial]({{< relref "../../Tutorials/CustomEvaluator/_index.md" >}}) for details.
 
 ### How to configure an Evaluator
 
@@ -73,7 +73,7 @@ Concurrently executing MatchFunctions fetch Tickets for their MatchProfiles from
 
 ### Overview of Synchronizer States
 
-Synchronizer's key role is to make sure that all the proposals generated by concurrent MatchFunctions get evaluated tgether. Further, the Synchronizer needs to halt function execution while the results are evaluated. Given that the MatchFunction is authored by the user, Open Match has no control over its execution time. However, Open Match has to make sure its results are evaluated with the other concurrent Match Functions - or are discarded if they missed the Evaluation time. To achieve this, the singleton Synchronizer component in Open Match has the following states:
+Synchronizer's key role is to make sure that all the proposals generated by concurrent MatchFunctions get evaluated together. Further, the Synchronizer needs to halt function execution while the results are evaluated. Given that the MatchFunction is authored by the user, Open Match has no control over its execution time. However, Open Match has to make sure its results are evaluated with the other concurrent Match Functions - or are discarded if they missed the Evaluation time. To achieve this, the singleton Synchronizer component in Open Match has the following states:
 
 #### Idle State
 

site/content/en/docs/Guides/custom.md renamed to site/content/en/docs/Guides/Custom/_index.md

@@ -39,11 +39,11 @@ To build a custom Matchmaker using Open Match, the user needs to provide the fol
 
 #### Match Function
 
-The core matchmaking logic is implemented as a Match Function service. Open Match Backend triggers the Match Function service when it receives a request to generate matches. The Match Function execution receives MatchProfiles, fetches Tickets that match the profile from QueryService and returns matches.
+The core matchmaking logic is implemented as a Match Function service. Open Match Backend triggers the Match Function service when it receives a request to generate Matches. The Match Function execution receives MatchProfiles, fetches Tickets that match the profile from QueryService and returns Matches.
 
 #### Evaluator (Optional)
 
-Open Match allows for concurrent Match Functions to execute on the same player pool. The matches generated by such concurrent Match Function executions may have overlapping Tickets. Given that one Ticket should only be used by a result, Open Match allows the user to plug in an Evaluator component to deduplicate matches before returning results. Open Match provides a default Evaluator which suffices for most common use cases. See [Evaluator Guide]({{< relref "../evaluator.md" >}}) for details on proposal evaluation.
+Open Match allows for concurrent Match Functions to execute on the same player pool. The Matches generated by such concurrent Match Function executions may have overlapping Tickets. Given that one Ticket should only be used by one resulting Match, Open Match allows the user to plug in an Evaluator component to deduplicate Match proposals before returning results. Open Match provides a default Evaluator which suffices for most common use cases. See [Evaluator Guide]({{< relref "../Evaluator/_index.md" >}}) for details on proposal evaluation.
 
 ### External Components
 
@@ -61,7 +61,7 @@ This is the component that receives the matchmaking request from the game client
 
 This is the component that understands the types of matches (MatchProfiles) that can be served and fetches matches
 from the Open Match Backend. The Director also interfaces with the DGS allocation system to fetch Game Servers for
-matches and creating Game Server Assignments from these details in Open Match, via communicating with the Open Match
+Matches and creating Game Server Assignments from these details in Open Match, via communicating with the Open Match
 Backend.
 
 ### Matchmaking Flow

site/content/en/docs/Guides/evaluator.md renamed to site/content/en/docs/Guides/Evaluator/_index.md

@@ -49,7 +49,7 @@ The configurations to enable/disable the telemetry exporters are not read at run
 {{% /alert %}}
 
 You can configure where and what telemetry you want to emit from your Open Match
-deployment. To instrument Open Match with telemetry supports, modify your `06-open-match-override-configmap.yaml` to override the related settings. Please refer to [how to customize your Open Match deployment]({{< relref "../custom.md/#telemetry" >}}) for more details.
+deployment. To instrument Open Match with telemetry supports, modify your `06-open-match-override-configmap.yaml` to override the related settings. Please refer to [how to customize your Open Match deployment]({{< relref "../Custom/_index.md/#telemetry" >}}) for more details.
 
 Below is an example of the data section in `om-configmap-override` configmap to enable all of the supported telemetry exporters:
 ```yaml

site/content/en/docs/Guides/Matchmaker/_index.md

@@ -9,7 +9,7 @@ description: >
 ## Prerequisites
 
 - [Helm](https://docs.helm.sh/helm/) package manager 3.0.0+
-- [Kuberentes](https://kubernetes.io) cluster, tested on Kubernetes version 1.13+
+- [Kubernetes](https://kubernetes.io) cluster, tested on Kubernetes version 1.13+
 
 ## Install the Open Match helm chart
 

site/content/en/docs/Guides/best_practices.md renamed to site/content/en/docs/Guides/Production/_index.md

@@ -57,9 +57,9 @@ Thus, starting the core service pods will remain in <code>ContainerCreating</cod
 
 - If you are proceeding with the [Getting Started]({{< relref "../Getting Started/_index.md" >}}), or following the [Tutorials]({{< relref "../Tutorials/_index.md" >}}), proceed with this guide to [install the default Evaluator]({{< ref "#install-the-default-evaluator" >}}) and configure Open Match to use it.
 
-- If you finished reading the tutorials and are building your own custom matchmaker and need to deploy a custom evaluator, then skip the next step and instead use the [Customization Guide]({{< relref "../Guides/custom.md" >}}) for steps to customize your Open Match installation.
+- If you finished reading the tutorials and are building your own custom matchmaker and need to deploy a custom evaluator, then skip the next step and instead use the [Customization Guide]({{< relref "../Guides/Custom/_index.md" >}}) for steps to customize your Open Match installation.
 
-## Install the default Evaluator
+## Install the Default Evaluator
 
 Run the below command to install the default Evaluator in the open-match namespace and to configure Open Match to use it.
 

site/content/en/docs/Guides/tls.md renamed to site/content/en/docs/Guides/TLS/_index.md

@@ -6,11 +6,6 @@ description: >
   Open Match is an open-source matchmaking framework that simplifies building your game matchmaker.
 ---
 
-## Disclaimer
-
-This software is currently [alpha](https://github.com/googleforgames/open-match/releases), and
-subject to change. Not to be used in production systems.
-
 ## What is Open Match
 
 Open Match is an open-source game matchmaking framework that simplifies building a scalable and extensible Matchmaker.