GA 2.0.0 release (#19)

Develop branch is ready for publication.

---------

Co-authored-by: silabs-akosj <146345861+silabs-akosj@users.noreply.github.com>

Author: AndrasZiegler

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# This is a # Default codeowners for the repository
+* @AndrasZiegler @silabs-TiborL

.github/CONTRIBUTING.md

@@ -0,0 +1,116 @@
+# Contributing to a SiliconLabs open source project
+
+You want to contribute to a Silicon Labs Open Source project? Welcome! Please read this document to understand what you can do:
+ * [Help Others](#help-others)
+ * [Analyze Issues](#analyze-issues)
+ * [Report an Issue](#report-an-issue)
+ * [Contribute Code](#contribute-code)
+
+## Help Others
+
+You can help the Silicon Labs open source projects by helping others who use them and need support.
+
+## Analyze Issues
+
+Analyzing issue reports can be a lot of effort. Any help is welcome!
+Go to [Issue tracker](https://github.com/SiliconLabsSoftware/bluetooth-AoA-example/issues?q=is%3Aopen+is%3Aissue)  and find an open issue which needs additional work or a bugfix (e.g. issues labeled with "help wanted" or "bug").
+
+Additional work could include any further information, or a gist, or it might be a hint that helps understanding the issue. Maybe you can even find and [contribute](#contribute-code) a bugfix?
+
+## Report an Issue
+
+If you find a bug - behavior of Silicon Labs Open Source projects code contradicting your expectation - you are welcome to report it.
+We can only handle well-reported, actual bugs, so please follow the guidelines below.
+
+Once you have familiarized with the guidelines, you can go to the [Create an issue](https://github.com/SiliconLabsSoftware/bluetooth-AoA-example/issues/new) to report the issue.
+
+### Quick Checklist for Bug Reports
+
+Issue report checklist:
+ * Real, current bug
+ * No duplicate
+ * Reproducible
+ * Good summary
+ * Well-documented
+ * Minimal example
+
+
+### Issue handling process
+
+When an issue is reported, a committer will look at it and either confirm it as a real issue, close it if it is not an issue, or ask for more details.
+
+An issue that is about a real bug is closed as soon as the fix is committed.
+
+
+### Reporting Security Issues
+
+If you find a security issue, please act responsibly and report it not in the public issue tracker, but directly to the CODE_OWNERS, so we can fix it before it can be exploited.
+
+
+### Usage of Labels
+
+GitHub offers labels to categorize issues. We defined the following labels so far:
+
+Labels for issue categories:
+ * bug: this issue is a bug in the code
+ * feature: this issue is a request for a new functionality or an enhancement request
+
+Status of open issues:
+ * help wanted: the feature request is approved and you are invited to contribute
+
+Status/resolution of closed issues:
+ * wontfix: while acknowledged to be an issue, a fix cannot or will not be provided
+
+The labels can only be set and modified by committers.
+
+
+### Issue Reporting Disclaimer
+
+We want to improve the quality of Silicon Labs Open Source projects and good bug reports are welcome! But our capacity is limited, thus we reserve the right to close or to not process insufficient bug reports in favor of those which are very cleanly documented and easy to reproduce. Even though we would like to solve each well-documented issue, there is always the chance that it will not happen - remember: these projects are open source and comes without warranty.
+
+Bug report analysis support is very welcome! (e.g. pre-analysis or proposing solutions)
+
+
+## Contribute Code
+
+You are welcome to contribute code to Silicon Labs Open Source projects in order to fix bugs or to implement new features.
+
+There are three important things to know:
+
+1.  You must be aware that you need to sign a [CLA](https://en.wikipedia.org/wiki/Contributor_License_Agreement) in order for your contribution to be accepted. This is common practice in all major Open Source projects.
+2.  There are **several requirements regarding code style, quality, and product standards** which need to be met (we also have to follow them). The respective section below gives more details on the coding guidelines.
+
+
+### Contribution Content Guidelines
+
+These are some of the rules we try to follow:
+
+-   Apply a clean coding style adapted to the surrounding code, even though we are aware the existing code is not fully clean
+-   Use (4)spaces for indentation (except if the modified file consistently uses tabs)
+-   Use variable naming conventions like in the other files you are seeing (camelcase)
+-   No console.log() - use logging service
+-   Run the ESLint code check and make it succeed
+-   Comment your code where it gets non-trivial
+-   Keep an eye on performance and memory consumption, properly destroy objects when not used anymore
+-   Write a unit test
+-   Do not do any incompatible changes, especially do not modify the name or behavior of public API methods or properties
+
+### How to contribute - the Process
+
+1.  Make sure the change would be welcome (e.g. a bugfix or a useful feature); best do so by proposing it in a GitHub issue
+2.  Create a branch forking the cla-assistant repository and do your change
+3.  Commit and push your changes on that branch
+4.  In the commit message
+ - Describe the problem you fix with this change.
+ - Describe the effect that this change has from a user's point of view. App crashes and lockups are pretty convincing for example, but not all bugs are that obvious and should be mentioned in the text.
+ - Describe the technical details of what you changed. It is important to describe the change in a most understandable way so the reviewer is able to verify that the code is behaving as you intend it to.
+5.  If your change fixes an issue reported at GitHub, add the following line to the commit message:
+    - ```Fixes #(issueNumber)```
+    - Do NOT add a colon after "Fixes" - this prevents automatic closing.
+6.  Create a Pull Request
+7.  Follow the link posted by the Silicon Labs Open Source projects to your pull request and accept it, as described in detail above.
+8.  Wait for our code review and approval, possibly enhancing your change on request
+    -   Note that the Silicon Labs Open Source projects developers also have their regular duties, so depending on the required effort for reviewing, testing and clarification this may take a while
+
+9.  Once the change has been approved we will inform you in a comment
+10.  We will close the pull request, feel free to delete the now obsolete branch

.github/Docker_readme.md

@@ -1,7 +1,7 @@
-# Build docker image
-
-Having a docker image for CICD is always a good way to secure the product development. Let's build a docker image.
-
-## Readme
-
-Please check the documentation in the main [README](../README.md) file.
+# Build docker image
+
+Having a docker image for CICD is always a good way to secure the product development. Let's build a docker image.
+
+## Readme
+
+Please check the documentation in the main [README](../README.md) file.

.github/build-docker-image.sh

@@ -1,53 +1,53 @@
-#!/bin/sh
-
-display_help() {
-    echo "Usage: $0 -i image_name -v version -r registry -a architecture " >&2
-    echo
-    echo "   -i image_name    Specify the image name, for example: devs_xg24_aoa_poc"
-    echo "   -v version       Specify the version of docker image, for example: 1.0.0"
-    echo "   -r registry      Specify the Docker registry to push the image to (optional) example: lx0017637.silabs.com:5000"
-    echo "                    If internal registry is used, SonarQube will be included."
-    echo "   -a architecture  Specify the architecture, for example: x86_64 or aarch64"
-    echo
-    exit 1
-}
-
-image_name=""
-version="1.0.0"
-registry="none"
-architecture="x86_64"
-run_sonarqube_scanner="false"
-
-# Process the options
-while getopts ":h:i:v:r:a:" opt; do
-  case $opt in
-    h) display_help
-       exit;;
-    i) image_name="$OPTARG";;
-    v) version="$OPTARG";;
-    r) registry="$OPTARG";;
-    a) architecture="$OPTARG";;
-    \?) echo "Invalid option -$OPTARG" >&2
-        display_help
-        exit 1;;
-    :) echo "Option -$OPTARG requires an argument." >&2
-       display_help
-       exit 1;;
-  esac
-done
-
-if [ "$registry" = "lx0017637.silabs.com:5000" ] ; then
-    echo "Internal silabs build with: $registry"
-    run_sonarqube_scanner="true"
-fi
-
-# Build the Docker image
-echo "Building Docker image: $image_name:$version for architecture: $architecture "
-docker build --build-arg ARCH="$architecture" --build-arg SONARQUBE="$run_sonarqube_scanner" -t "$image_name:$version" -f Dockerfile .
-
-if [ -n "$registry" ] && [ "$registry" != "none" ] ; then
-    docker tag "$image_name:$version" "$registry/$image_name:$version"
-    docker push "$registry/$image_name:$version"
-else
-    echo "Docker registry not specified, skipping tagging and pushing."
-fi
+#!/bin/sh
+
+display_help() {
+    echo "Usage: $0 -i image_name -v version -r registry -a architecture " >&2
+    echo
+    echo "   -i image_name    Specify the image name, for example: devs_xg24_aoa_poc"
+    echo "   -v version       Specify the version of docker image, for example: 1.0.0"
+    echo "   -r registry      Specify the Docker registry to push the image to (optional) example: lx0017637.silabs.com:5000"
+    echo "                    If internal registry is used, SonarQube will be included."
+    echo "   -a architecture  Specify the architecture, for example: x86_64 or aarch64"
+    echo
+    exit 1
+}
+
+image_name=""
+version="1.0.0"
+registry="none"
+architecture="x86_64"
+run_sonarqube_scanner="false"
+
+# Process the options
+while getopts ":h:i:v:r:a:" opt; do
+  case $opt in
+    h) display_help
+       exit;;
+    i) image_name="$OPTARG";;
+    v) version="$OPTARG";;
+    r) registry="$OPTARG";;
+    a) architecture="$OPTARG";;
+    \?) echo "Invalid option -$OPTARG" >&2
+        display_help
+        exit 1;;
+    :) echo "Option -$OPTARG requires an argument." >&2
+       display_help
+       exit 1;;
+  esac
+done
+
+if [ "$registry" = "lx0017637.silabs.com:5000" ] ; then
+    echo "Internal silabs build with: $registry"
+    run_sonarqube_scanner="true"
+fi
+
+# Build the Docker image
+echo "Building Docker image: $image_name:$version for architecture: $architecture "
+docker build --build-arg ARCH="$architecture" --build-arg SONARQUBE="$run_sonarqube_scanner" -t "$image_name:$version" -f Dockerfile .
+
+if [ -n "$registry" ] && [ "$registry" != "none" ] ; then
+    docker tag "$image_name:$version" "$registry/$image_name:$version"
+    docker push "$registry/$image_name:$version"
+else
+    echo "Docker registry not specified, skipping tagging and pushing."
+fi

.github/build-with-docker.sh

@@ -1,61 +1,61 @@
-#!/bin/sh
-
-display_help() {
-    echo "Usage: $0 -i image_name -v version -r registry -a architecture -c clean" >&2
-    echo
-    echo "   -i image_name    Specify the image name, for example: devs_xg24_aoa_poc"
-    echo "   -v version       Specify the version of docker image, for example: 1.0.0"
-    echo "   -r registry      Specify the Docker registry to push the image to"
-    echo "   -a architecture  Specify the architecture, for example: x86_64 or aarch64 (optional)"
-    echo "   -c clean         Specify 'clean' to remove the built Docker image"
-    echo
-    exit 1
-}
-
-image_name="devs_xg24_aoa_poc"
-version="1.0.0"
-registry="none"
-architecture="x86_64"
-clean="false"
-
-while getopts ":hi:v:r:a:c" opt; do
-  case ${opt} in
-    h )
-      display_help
-      exit 1;;
-    i )
-      image_name=$OPTARG;;
-    v )
-      version=$OPTARG;;
-    r )
-      registry=$OPTARG;;
-    a )
-      architecture=$OPTARG;;
-    c )
-      clean="true";;
-    \? )
-      display_help
-      exit 1 ;;
-    : )
-      echo "Invalid option: $OPTARG requires an argument" 1>&2
-      display_help
-      exit 1 ;;
-  esac
-done
-shift $((OPTIND -1))
-
-echo "<----- Docker based Weber Wasp project building script ----->"
-
-echo "Calling the docker image builder script..."
-
-# Call build-docker-image.sh with arguments
-sh ./.github/build-docker-image.sh -i $image_name -v $version -r $registry -a $architecture || { echo "Failed to build the Docker image"; exit 1; }
-
-echo "<----- Running the docker based build environment ----->"
-# Run the docker image
-docker run -u root --rm -v $(pwd):/home/jenkins/devs_xg24_aoa_poc $image_name:$version /bin/sh -c "cd devs_xg24_aoa_poc && make all"
-
-if [ "$clean" = "true" ]; then
-    docker rmi $image_name:$version
-    echo "Clean mode activated. Docker image $image_name:$version is removed."
-fi
+#!/bin/sh
+
+display_help() {
+    echo "Usage: $0 -i image_name -v version -r registry -a architecture -c clean" >&2
+    echo
+    echo "   -i image_name    Specify the image name, for example: devs_xg24_aoa_poc"
+    echo "   -v version       Specify the version of docker image, for example: 1.0.0"
+    echo "   -r registry      Specify the Docker registry to push the image to"
+    echo "   -a architecture  Specify the architecture, for example: x86_64 or aarch64 (optional)"
+    echo "   -c clean         Specify 'clean' to remove the built Docker image"
+    echo
+    exit 1
+}
+
+image_name="devs_xg24_aoa_poc"
+version="1.0.0"
+registry="none"
+architecture="x86_64"
+clean="false"
+
+while getopts ":hi:v:r:a:c" opt; do
+  case ${opt} in
+    h )
+      display_help
+      exit 1;;
+    i )
+      image_name=$OPTARG;;
+    v )
+      version=$OPTARG;;
+    r )
+      registry=$OPTARG;;
+    a )
+      architecture=$OPTARG;;
+    c )
+      clean="true";;
+    \? )
+      display_help
+      exit 1 ;;
+    : )
+      echo "Invalid option: $OPTARG requires an argument" 1>&2
+      display_help
+      exit 1 ;;
+  esac
+done
+shift $((OPTIND -1))
+
+echo "<----- Docker based Weber Wasp project building script ----->"
+
+echo "Calling the docker image builder script..."
+
+# Call build-docker-image.sh with arguments
+sh ./.github/build-docker-image.sh -i $image_name -v $version -r $registry -a $architecture || { echo "Failed to build the Docker image"; exit 1; }
+
+echo "<----- Running the docker based build environment ----->"
+# Run the docker image
+docker run -u root --rm -v $(pwd):/home/jenkins/devs_xg24_aoa_poc $image_name:$version /bin/sh -c "cd devs_xg24_aoa_poc && make all"
+
+if [ "$clean" = "true" ]; then
+    docker rmi $image_name:$version
+    echo "Clean mode activated. Docker image $image_name:$version is removed."
+fi