Changed microROS to micro-ROS in most texts and in those urls where repo has been already moved.

ralph-lange · ralph-lange · commit 8f6c56e6167f · 2019-04-17T14:55:20.000+02:00
Signed-off-by: Ralph Lange (CR/AEE1) &lt;ralph.lange@de.bosch.com&gt;
diff --git a/README.md b/README.md
@@ -1,15 +1,15 @@
-# microROS web site
+# micro-ROS web site
 
-This is the source for the microROS website, available 
-at [https://microros.github.io/](https://microros.github.io/)
+This is the source for the micro-ROS website, available
+at [https://micro-ros.github.io/](https://micro-ros.github.io/)
 
 ## Editing
 
 See [editing instructions](EDITING-INSTRUCTIONS.md)
 
 ## Running locally
 
-To test locally, you need a local version of Jekyll, the site-generation 
+To test locally, you need a local version of Jekyll, the site-generation
 engine used by Github Pages. See [Jekyll Quickstart](https://jekyllrb.com/docs/)
 for installation instructions.
 
@@ -28,7 +28,7 @@ To install it, It has been incorporated in the Gemfile so the previous dependenc
 
 You can run the following gem to tests the generated site.
 
-```bash 
+```bash
 bundle exec jekyll build
 bundle exec htmlproofer ./_site
 ```
diff --git a/_docs/FIROS2/index.md b/_docs/FIROS2/index.md
@@ -1,13 +1,13 @@
 ---
-title: microROS & FIWARE
+title: micro-ROS & FIWARE
 permalink: /docs/FIROS2/
 redirect_from: /FIROS2/
 ---
 
 
 ## Interoperability
 
-This subsection will explain all the design alternatives for the interoperability of FIROS2 with microROS.
+This subsection will explain all the design alternatives for the interoperability of FIROS2 with micro-ROS.
 
 ### Mechanisms for the deserialisation of incoming data in the transformation library
 
@@ -25,7 +25,7 @@ For solving this issue, various methods to get it are proposed:
 
 #### Use serialisation/deserialisation method provided by the middleware layer
 
-This is currently the method used in microROS - FIROS 2 integration.
+This is currently the method used in micro-ROS - FIROS 2 integration.
 
 In this case, the transformation library will use user selected middleware interface to serialise/deserialise the bridged ROS2 messages.
 This method requires to get the message typesupport for the bridged message type.
@@ -63,25 +63,25 @@ Note the call to ROS 2 interface __rosidl_typesupport_cpp::get_message_type_supp
 #### Use serialisation/deserialisation method for an specific type support
 
 In this case, the transformation library will use one specific type support to serialise/deserialise the bridged ROS2 messages.
-In microROS case, the implementation to be used will be rosidl_typesupport_microxrcedds.
+In micro-ROS case, the implementation to be used will be rosidl_typesupport_microxrcedds.
 This method is trivial to develop as it does not require additional source code on the micro-ROS side.
 
-In the case of microROS, the transformation library should use the serialisation/deserialisation API exposed by its typesupport, rosidl_typesupport_microxrcedds.
+In the case of micro-ROS, the transformation library should use the serialisation/deserialisation API exposed by its typesupport, rosidl_typesupport_microxrcedds.
 This mechanism requires the user to have access to the typesupport API, which sometimes is not always possible.
 
 #### Used serialisation/deserialisation method generated from IDL file
 
 In this case, transformation library will use generated code to serialise/deserialise the bridged ROS2 messages.
 The generated code may be made using an IDL parser tool.
-In the microROS case, Micro XRCE-DDS provides with Micro XRCE-DDS code generator, which accepts an IDL file as input and generates type code.
+In the micro-ROS case, Micro XRCE-DDS provides with Micro XRCE-DDS code generator, which accepts an IDL file as input and generates type code.
 This IDL files should correspond with those messages types the transformation is wanted.
 This is the [integration service](https://github.com/eProsima/Integration-Service) native method.
 Integration services uses this method, but it makes the development of the library slower as it needs to be generated per each message to be bridged.
 
 ![image](http://www.plantuml.com/plantuml/svg/bP8_2y8m4CNtV8f7tOIArd-R2DR1GGTT70eIqciRQ1D8qkzl4sr1iA0t11xlxjsF97lhk75jKxEQ2WUdOMHPEUJIa71IAwPqJeZGLQOoTPR2QDolXsESfZS8RvQao72dZM_mZH6unIbzB32XENN52baF8GrPoql20ZAluPtFgGIiGv855mvHfcwwDO9UcmfjC8ptsp2TYH1Z1rtrEbDzwX9V8P8HYDLl4Cb_4Ell49SHYCrl49V_8BPWZ8LxZkFTwvbOEDzo6UHgn5q7kHbnk-mzgTp_foS0)
 
-In the case of ROS2/microROS workspaces, there are tools which generate those IDL files.
-The rosidl_gen package is the package microROS/ROS2 could use to create IDL from ROS2 interfaces.
+In the case of ROS2/micro-ROS workspaces, there are tools which generate those IDL files.
+The rosidl_gen package is the package micro-ROS/ROS2 could use to create IDL from ROS2 interfaces.
 
 ### Integration proposals
 
@@ -90,7 +90,7 @@ This section presents all the integrations possibilities.
 
 #### Direct integration
 
-In this case, microROS Agent will act as a bridge between DDS-XRCE and NGSIv2.
+In this case, micro-ROS Agent will act as a bridge between DDS-XRCE and NGSIv2.
 
 Selected bridged topics and their corresponding transformations must be configured on the micro-ROS Agent node.
 
@@ -106,7 +106,7 @@ This proposal requires micro-ROS Agent changes, but it is the direct native inte
 
 #### Indirect integration with a single FIROS2 node
 
-In this case, microROS nodes will publish the configured topics on DDS, and a FIROS2 node will subscribe to those topics and convert them into NGSIv2 protocol.
+In this case, micro-ROS nodes will publish the configured topics on DDS, and a FIROS2 node will subscribe to those topics and convert them into NGSIv2 protocol.
 Selected bridged topics must be configured on that single FIROS2 node.
 Each ROS 2 topic type should have a corresponding transformation library configured on that FIROS2 node.
 
@@ -124,11 +124,11 @@ This proposal requires transformation library development, but the integration w
 
 #### Indirect integration with multiple FIROS2 nodes
 
-In this case, microROS nodes will publish the configured topic on DDS and multiple FIROS2 nodes, one for each set topic, will subscribe to those topics and convert them into NGSIv2 protocol.
+In this case, micro-ROS nodes will publish the configured topic on DDS and multiple FIROS2 nodes, one for each set topic, will subscribe to those topics and convert them into NGSIv2 protocol.
 
 This approach would require more nodes on the network and individual configurations.
 
-This approach is the one followed by microROS, and it is limited due to current FIROS 2 implementation.
+This approach is the one followed by micro-ROS, and it is limited due to current FIROS 2 implementation.
 
 This proposal requires transformation library development, but the integration will be the same as a regular ROS2 node, so no micro-ROS specific development should be expected.
 
diff --git a/_docs/embedded_tf/index.md b/_docs/embedded_tf/index.md
@@ -18,7 +18,7 @@ Table of contents
 
 The TF transform graph, with its support for both a temporal history, and distributed information sources, has been a novel tool for robotics frameworks when it was released in 2008. Functionally, it is based in scene graph concepts known from computer graphics [[Foote 2013]](https://ieeexplore.ieee.org/document/6556373), but these only rarely offer distribution, and did not offer temporal histories at all (mainly, because this is not needed for frame-based rendering applications like in computer graphics). Distributed scene graphs have become more widely available also in computer graphics. In robotics, work by de Laet et al. [[De Laet et al. 2013]](https://ieeexplore.ieee.org/document/6696693) has extended transforms graphs to also contain twist (i.e., angular motion) information, and to provide more compile-time error checking. This is currently not integrated with distribution mechanisms, but could be used on a single system.
 One persistent issue with transform graphs has been their resource use. ROS TF works through replicated copies of the entire transform tree at every node that uses it, and is implemented through unicast TCP connections between nodes. In systems with many dynamic parts, this has sometimes been called the ``TF firehose``, because of the large stream of incoming messages.
-micro-ROS will go beyond this state of the art by running the dynamic transform tree in an embedded device, while keeping resource use to a minimum based on an analysis of the spatial and temporal details actually necessary. Further, enabling real-time queries even in the face of concurrent updates through integration will be realized through integration with the microROS real-time executor. It is also planned to integrate the embedded TF will with the node lifecycle to achieve further power-savings
+micro-ROS will go beyond this state of the art by running the dynamic transform tree in an embedded device, while keeping resource use to a minimum based on an analysis of the spatial and temporal details actually necessary. Further, enabling real-time queries even in the face of concurrent updates through integration will be realized through integration with the micro-ROS real-time executor. It is also planned to integrate the embedded TF will with the node lifecycle to achieve further power-savings
 
 
 ## Requirements
diff --git a/_docs/hardware_support.md b/_docs/hardware_support.md
@@ -1,8 +1,8 @@
 ---
 title: Supported Hardware
---- 
+---
 
-This page lists the hardware that microROS currently supports, and also accessories that we frequently refer to, such as add-on boards, and JTAG probes.
+This page lists the hardware that micro-ROS currently supports, and also accessories that we frequently refer to, such as add-on boards, and JTAG probes.
 
 ## Evaluation Boards
 
@@ -17,4 +17,4 @@ This is a fairly bare-bones evaluation board with an STM32F407ZGT6 microcontroll
 This is a JTAG probe with a USB and RS232 port that can also power the board. It looks as follows:
 ![image of ARM-USB-OCD-H](https://www.olimex.com/Products/ARM/JTAG/ARM-USB-OCD-H/images/thumbs/310x230/ARM-USB-OCD-H-2.png)
 
-See the [Olimex product page for ARM-USB-OCD-H](https://www.olimex.com/Products/ARM/JTAG/ARM-USB-OCD-H/) for details.
+See the [Olimex product page for ARM-USB-OCD-H](https://www.olimex.com/Products/ARM/JTAG/ARM-USB-OCD-H/) for details.
diff --git a/_docs/index.md b/_docs/index.md
@@ -3,7 +3,7 @@ permalink: /docs/home/
 title: Overview
 ---
 
-[microROS](https://cordis.europa.eu/project/rcn/213167_en.html) puts ROS2 onto microcontrollers, making them first class participants of the ROS 2 environment.
+[micro-ROS](https://cordis.europa.eu/project/rcn/213167_en.html) puts ROS2 onto microcontrollers, making them first class participants of the ROS 2 environment.
 
 ## Tutorials
 
diff --git a/_docs/real-time_executor/index.md b/_docs/real-time_executor/index.md
@@ -74,7 +74,7 @@ In this section, we describe the necessary changes to the Executor API and repor
 
 ### API Changes
 
-*   [include/rclcpp/callback\_group.hpp](https://github.com/microROS/rclcpp/blob/cbg-executor-0.5.1/rclcpp/include/rclcpp/callback_group.hpp):
+*   [include/rclcpp/callback\_group.hpp](https://github.com/micro-ROS/rclcpp/blob/cbg-executor-0.5.1/rclcpp/include/rclcpp/callback_group.hpp):
 
     Introduced enum to distinguish up to three real-time classes (requirements) per node.
 
@@ -102,7 +102,7 @@ In this section, we describe the necessary changes to the Executor API and repor
     }
     ```
 
-*   [include/rclcpp/executor.hpp](https://github.com/microROS/rclcpp/blob/cbg-executor-0.5.1/rclcpp/include/rclcpp/executor.hpp)
+*   [include/rclcpp/executor.hpp](https://github.com/micro-ROS/rclcpp/blob/cbg-executor-0.5.1/rclcpp/include/rclcpp/executor.hpp)
 
     Added functions to add and remove individual callback groups in addition to whole nodes.
 
@@ -136,11 +136,11 @@ In this section, we describe the necessary changes to the Executor API and repor
     WeakCallbackGroupsToNodesMap weak_groups_to_nodes_;
     ```
 
-*   [include/rclcpp/memory\_strategy.hpp](https://github.com/microROS/rclcpp/blob/cbg-executor-0.5.1/rclcpp/include/rclcpp/memory_strategy.hpp)
+*   [include/rclcpp/memory\_strategy.hpp](https://github.com/micro-ROS/rclcpp/blob/cbg-executor-0.5.1/rclcpp/include/rclcpp/memory_strategy.hpp)
 
     Changed all functions that expect a vector of nodes to the just mentioned map.
 
-*   [include/rclcpp/node.hpp](https://github.com/microROS/rclcpp/blob/cbg-executor-0.5.1/rclcpp/include/rclcpp/node.hpp) and [include/rclcpp/node_interfaces/node_base.hpp](https://github.com/microROS/rclcpp/blob/cbg-executor-0.5.1/rclcpp/include/rclcpp/node_interfaces/node_base.hpp)
+*   [include/rclcpp/node.hpp](https://github.com/micro-ROS/rclcpp/blob/cbg-executor-0.5.1/rclcpp/include/rclcpp/node.hpp) and [include/rclcpp/node_interfaces/node_base.hpp](https://github.com/micro-ROS/rclcpp/blob/cbg-executor-0.5.1/rclcpp/include/rclcpp/node_interfaces/node_base.hpp)
 
     Extended arguments of create\_callback\_group function for the real-time class.
 
@@ -153,7 +153,7 @@ In this section, we describe the necessary changes to the Executor API and repor
 
     Removed the get\_associated\_with\_executor\_atomic function.
 
-All the changes can be found in the branches [cbg-executor-0.5.1](https://github.com/microROS/rclcpp/tree/cbg-executor-0.5.1/rclcpp) and [cbg-executor-0.6.1](https://github.com/microROS/rclcpp/tree/cbg-executor-0.6.1/rclcpp) for the corresponding version 0.5.1 and 0.6.1 of the rclcpp in the fork at [github.com/microROS/rclcpp/](https://github.com/microROS/rclcpp/).
+All the changes can be found in the branches [cbg-executor-0.5.1](https://github.com/micro-ROS/rclcpp/tree/cbg-executor-0.5.1/rclcpp) and [cbg-executor-0.6.1](https://github.com/micro-ROS/rclcpp/tree/cbg-executor-0.6.1/rclcpp) for the corresponding version 0.5.1 and 0.6.1 of the rclcpp in the fork at [github.com/micro-ROS/rclcpp/](https://github.com/micro-ROS/rclcpp/).
 
 
 ### Meta-Executor Concept
@@ -175,7 +175,7 @@ With the test bench, we validated the functioning of the approach - here on ROS
 
 ![Results from Callback-group-level Executor test bench](cbg-executor_test-bench_results.png)
 
-The test bench is provided in the [bg-executor_ping-pong_cpp](https://github.com/microROS/microROS_experiments/tree/experiment/cbg-executor-0.6.1/cbg-executor_ping-pong) package of the [microROS_experiments](https://github.com/microROS/microROS_experiments) repository.
+The test bench is provided in the [bg-executor_ping-pong_cpp](https://github.com/micro-ROS/micro-ROS_experiments/tree/experiment/cbg-executor-0.6.1/cbg-executor_ping-pong) package of the [micro-ROS_experiments](https://github.com/micro-ROS/micro-ROS_experiments) repository.
 
 
 ## Roadmap
diff --git a/_docs/tutorials/advanced/nuttx_getting_started/index.md b/_docs/tutorials/advanced/nuttx_getting_started/index.md
@@ -1122,7 +1122,7 @@ And it should look like this:
 Now the board it's ready.
 Connect the serial cable (TTL232) to the computer and check which is the number of the serial port.
 
-Note: We need to install previously the microROS agent. So you can follow the next guide to install it:
+Note: We need to install previously the micro-ROS agent. So you can follow the next guide to install it:
 https://github.com/microROS/micro-ROS-doc/blob/master/docs/install_and_run.md
 
 ## Run a publisher:
diff --git a/_posts/2018-09-30-roscon.md b/_posts/2018-09-30-roscon.md
@@ -1,11 +1,11 @@
 ---
-title: microROS@ROSCon2018
+title: micro-ROS@ROSCon2018
 author: ralph-lange
 ---
 
 ROSCon ([https://roscon.ros.org](https://roscon.ros.org/)) is the most important event of the ROS community. ROSCon has grown remarkably in the last years. In 2018, the conference was sold out already during the early registration phase. 500 developers and researchs from all over the globe attended ROSCon 2018 in Madrid. More than 1000 watched the live stream.
 
-Several people from the microROS team attended the conference and delivered talks and demonstrations. In sum, three talks related to microROS were provided:
+Several people from the micro-ROS team attended the conference and delivered talks and demonstrations. In sum, three talks related to micro-ROS were provided:
 
 **Iñigo Muguruza Goenaga (Erle Robotics), Juan Flores Muñoz (Erle Robotics), Víctor Mayoral Vilches (Erle Robotics), Loïc Dauphin (INRIA), Emmanuel Baccelli (INRIA), Cedric Adjih (INRIA): Towards ROS 2 microcontroller meta cross-compilation**
 
diff --git a/_posts/2018-11-13-ros-dev-podcast-ralph-lange.md b/_posts/2018-11-13-ros-dev-podcast-ralph-lange.md
@@ -5,7 +5,7 @@ author: ralph-lange
 
 The ROS Developers Podcast ([www.theconstructsim.com/category/ros_developers_podcast/](http://www.theconstructsim.com/category/ros_developers_podcast/)) was launched by [The Construct](http://www.theconstructsim.com/)'s CEO Ricardo Téllez. On a weekly to biweekly basis, he publishes a half-hour interview with developers from the ROS community.
 
-In [**episode 29**](http://www.theconstructsim.com/rdp-029-bosch-ros-projects-ralph-lange/), from November 2018, Ralph Lange from Bosch was interviewed. He presented several works related to microROS, including the Callback-group-level Executor and the system modes concept. Ralph particularly emphasized the need for real-time execution mechanisms in ROS 2 and microROS.
+In [**episode 29**](http://www.theconstructsim.com/rdp-029-bosch-ros-projects-ralph-lange/), from November 2018, Ralph Lange from Bosch was interviewed. He presented several works related to microROS, including the Callback-group-level Executor and the system modes concept. Ralph particularly emphasized the need for real-time execution mechanisms in ROS 2 and micro-ROS.
 
 <iframe style="border: none" src="//html5-player.libsyn.com/embed/episode/id/7540592/height/90/theme/custom/thumbnail/yes/direction/backward/render-playlist/no/custom-color/87A93A/" height="90" width="100%" scrolling="no"  allowfullscreen webkitallowfullscreen mozallowfullscreen oallowfullscreen msallowfullscreen></iframe>
 
diff --git a/_posts/2018-12-14-ric-eu.md b/_posts/2018-12-14-ric-eu.md
@@ -1,11 +1,11 @@
 ---
-title: microROS@ROS Industrial 2018
+title: micro-ROS@ROS Industrial 2018
 author: lui3si
 ---
 
 The [ROS Industrial Conference](https://rosindustrial.org/events/2018/12/11/ros-industrial-conference-2018) is one of the biggest gatherings of ROS users in Europe, focusing largely on automation, but also covering many related topics.
 
-Several people from the microROS team were there and both Víctor Mayoral Vilches and Ingo Lütkebohle gave talks.
+Several people from the micro-ROS team were there and both Víctor Mayoral Vilches and Ingo Lütkebohle gave talks.
 
 ## Talk Links
 
@@ -23,4 +23,4 @@ Thanks to the ROS Industrial Team for inviting us and making the nice videos ava
 ## Summary Video
 
 There's also a nice summary video available
-<iframe width="560" height="315" src="https://www.youtube.com/embed/YRxuWC1LNAQ" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+<iframe width="560" height="315" src="https://www.youtube.com/embed/YRxuWC1LNAQ" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
diff --git a/_posts/2019-02-26-site-revamped.md b/_posts/2019-02-26-site-revamped.md
@@ -1,6 +1,6 @@
 ---
-title:  "microROS site re-organized, tutorials added"
+title:  "micro-ROS site re-organized, tutorials added"
 author: lui3si
 ---
 
-Previously we had documentation in three different repos, which was a bit confusing. So, now, we've brought everything together and you can just browse the [docs](/docs/home) section!
+Previously we had documentation in three different repos, which was a bit confusing. So, now, we've brought everything together and you can just browse the [docs](/docs/home) section!
