Rename GitHub Actions and add industrial CI. Remove AWS people from maintainers.

.github/workflows/ci.yml

+name: CI
+on:
+  pull_request:
+  push:
+  schedule:
+    # Run every morning to detect flakiness and broken dependencies
+    - cron: '28 6 * * *'
+
+jobs:
+  industrial_ci:
+    strategy:
+      matrix:
+        env:
+          - {ROS_DISTRO: foxy, ROS_REPO: testing}
+          - {ROS_DISTRO: foxy, ROS_REPO: main}
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v1
+      - uses: 'ros-industrial/industrial_ci@master'
+        env: ${{matrix.env}}

.github/workflows/test.yml → .github/workflows/code_coverage.yml

-name: Test ros2_control_demos
+name: Coverage
 on:
   pull_request:
   push:

.github/workflows/lint.yml → .github/workflows/linters.yaml

-name: Lint ros2_control_demos
+name: Linters
 on:
   pull_request:
 

README.md

+# ROS2 Control Demos
+
+.. image:: https://github.com/ros-controls/ros2_control_demos/workflows/CI/badge.svg?branch=master
+    :target: https://github.com/ros-controls/ros2_control_demos/actions
+    :alt: CI - GitHub Actions status
+.. image:: https://github.com/ros-controls/ros2_control_demos/workflows/Linters/badge.svg?branch=master
+    :target: https://github.com/ros-controls/ros2_control_demos/actions
+    :alt: Linters - GitHub Actions status
+.. image:: https://github.com/ros-controls/ros2_control_demos/workflows/Coverage/badge.svg?branch=master
+    :target: https://github.com/ros-controls/ros2_control_demos/actions
+    :alt: Code Coverage - GitHub Actions status
+
+This repository provides templates for the development of `ros2_control`-enabled robots and a simple simulation of a robot to demonstrate and prove `ros2_control` concepts.
+
+.. contents:: Table of Contents
+   :depth: 2
+
+## Goals
+
 The repository has two goals:
 
 1. It provides templates for faster start of implementing own hardware and controllers;
-2. The repository is a validation environment for `ros2_control` concepts, which can only be tested during run-time (e.g., execution of controllers by the controller manager,  communication between robot hardware and controllers). 
+2. The repository is a validation environment for `ros2_control` concepts, which can only be tested during run-time (e.g., execution of controllers by the controller manager,  communication between robot hardware and controllers).
 
-# ROS2 Control Demos
 
-This repository provides templates for the development of `ros2_control`-enabled robots and a simple simulation of a robot to demonstrate and prove `ros2_control` concepts.
+## Description
+
 The repository is inspired by [ros_control_boilerplate](https://github.com/PickNikRobotics/ros_control_boilerplate) repository from Dave Coleman.
 The simulation has three parts/packages:
 1. The first package, `ros2_control_demo_communication_headless`, uses scripts to simulate communication to and movements of virtual hardware.

ros2_control_demos/package.xml

@@ -7,10 +7,9 @@
   <author email="ostasse@laas.fr">Olivier Stasse</author>
   <author email="denis@stogl.de">Denis Štogl</author>
 
-  <maintainer email="allabana@amazon.com">Anas Abou Allaban</maintainer>
+  <maintainer email="karsten@openrobotics.org">Karsten Knese</maintainer>
   <maintainer email="bence.magyar.robotics@gmail.com">Bence Magyar</maintainer>
   <maintainer email="jordan.palacios@pal-robotics.com">Jordan Palacios</maintainer>
-  <maintainer email="karsten@openrobotics.org">Karsten Knese</maintainer>
   <maintainer email="ostasse@laas.fr">Olivier Stasse</maintainer>
   <maintainer email="denis@stogl.de">Denis Štogl</maintainer>