Tasks regarding the webpage restructuring as discussed during the OFERA f2f meeting of 14.10.2020

• Landing Page: Add a list of main features @ralph-lange

• Overview section

  • Architecture
    • Update/rework Architecture diagram @ralph-lange
    • Link each layer to associated features, according to this document @ralph-lange
    • Remove ‘Source Code Repositories’ part, and move it to the ‘Docker and CI status’ @FranFin
  • Feature Status
    • Now meant to represent comparison with features of ROS 2: change name accordingly @ralph-lange
    • Update/add/delete features. Missing: @ralph-lange
      • Actions
      • Graphs
      • Parameters
      • Discovery
      • QoS?
      • p2p (or explain difference between new p2p and CED middleware)
      • Operations within a ROS 2 node
      • Support for RT code - add sentence regarding rclpy and rclcpp
    • Add third column for symbols that encode features status [Done; Done partially; WIP; Not done but envisioned in the very near future; Not done and not planned] + Legend @FranFin
    • Split table into sub-tables: group features by category that +- represent the features list presented in 'Landing page' and ‘Architecture’. Small headings in bold between categories. @FranFin
  • Supported Hardware @pablogs9 ---> Rework hardware page #241
    • Change appearance: only logos, and then you get the info when clicking on the logo
    • Add sentence explaining that more boards have been ported by users and link to table in micro_ros_setup README
  • Supported RTOSes [page to be created]: Add RTOSes in the same form as the hardware, with clickable logos with short description (while removing them from ‘Concepts’ page) @FranFin
  • Transport and Data Links: Change the table to be more similar (or even equal) to the one that is found in the micro_ros_setup README (specifying which transports are allowed for each available combination of HW and RTOS) ---> Rework transports tables #243 @pablogs9
  • Docker and CI status @jamoralp -> Update Docker and CI status tables and content #248
    • Rename as ‘Repositories, Dockers and CI status’
    • Add ‘Source Code Repositories’ part from ‘Architecture’, and update it
    • Update Docker and CI status part
  • Members, partners and users @FranFin
    • Add new partners and MW users
    • Add 'Collaborators' section
  • Licensing [page to be created]: Add category explaining micro-ROS' licenses @ralph-lange

• Concepts section

  • Client library @ralph-lange
    • Intro to Client library
      • Rewrite text and Rework diagram
      • Reduce importance of rclcpp and specify that we don’t use it much
      • Introduce the rclc
      • rcl and rcutils: explain differences with respect to that of ROS 2
      • Link ‘Programming with rcl and rclc’ in the Tutorials section
    • Embedded Transform: remove
    • Decision paper -> moved to a PDF (as discussed in later OFERA meeting)
  • Middleware
    • Micro XRCE-DDS @FranFin
      • Update text (e. g. mention FreeRTOS and Zephyr)
      • Link ‘Middleware Configuration’ in the Tutorials section
      • Mention rmw and link rmw_microxrcedds readme
      • Link to ‘custom QoS’ tutorials
      • Add memory profiling of Micro XRCE-DDS
    • micro-ROS and FIWARE: move it to standalone section, under the name "Interoperability with FIWARE" @jamoralp -> Rework FIWARE interoperability section #249
    • micro-ROS compared to rosserial: change name to "Micro XRCE-DDS compared to rosserial" @FranFin
  • RTOS @FranFin
    • Why a Real-Time Operating System?: Add RTOSes logos at the end, that redirect to new pages in the Overview Section
    • FreeRTOS/NuttX/Zephyr: Remove and pass descriptions to Overview section
    • Integration with colon: Remove. The sentence can be added to the only section that will be left (Why a Real-Time Operating System?)
  • micro-ROS' build system [page to be added] ---> Adding build systems section #244 @pablogs9
    • Section dedicated to standard build system
    • Section dedicated to micro-ROS as a component in external development environments
  • Benchmarking: Rework in order to provide results of benchmarking @amx-piap
  • micro-ROS memory profiling [page to be added]: material here @FranFin

• Tutorials section: NuttX-specific tutorials: Add a disclaimer specifying that they are currently unmaintained. ---> Add unmainained disclaimer in Nuttx tutorials #242 @pablogs9

• Demos section:

  • Rewrite overview page
  • Add MoveIt demo @FranFin
  • Add ROS 2 to micro-ROS TCP tunneling over WAN via IS demo @FranFin
  • Add PIAP demo @amx-piap