Add modification to documentation of Mender conversion tool:
1. Comments on Device integration section (will follow up with Artifacts):
- The note "Mender has four reference devices already integrated..." is duplicated on https://docs.mender.io/development/devices/system-requirements and https://docs.mender.io/development/devices/system-requirements/yocto
- Why are we tailoring the conversion script to BeagleBone and Raspberry Pi 3 on https://docs.mender.io/development/devices/system-requirements/debian-family ? The goal is to make this device-agnostic? Would remove any mention of specific devices and say that this approach should work on most Debian-based devices, including Raspbian and Ubuntu.
- On the same page, it uses "Fedora 28" as an example workstation, while we use Ubuntu 18 as the default in other parts of the docs. I think we should continue to use Ubuntu 18, it will be quite confusing if some parts of the docs assume Ubuntu, and other parts Fedora.[
- As a new user with Debian, Raspbian or Ubuntu, what are the exact steps I need to do? Right now it seems like there are some dependencies to install (https://docs.mender.io/development/devices/system-requirements/debian-family) and then bootloader installation (https://docs.mender.io/development/devices/system-requirements/debian-family/bootloader-support). Why are these on two different pages? Is there a case where I just need to do one of these? Maybe these can be removed, as we already have https://docs.mender.io/development/artifacts/building-mender-image/building-debian-image
- What is the name for this new feature? I see it referred to as "Mender conversion scripts", "Mender conversion tools" and simply "Mender scripts". In the repo it seems to be called "Mender conversion tool". Should we update all references to that?
- Would consider organizing Devices differently. For things that are truly OS agnostic (e.g. System requirements, Partition layout), it can be a top level item. But then would organize by OS below this level. E.g. Device integration -> Yocto Porject -> Integrating with GRUB, rather than -> Device integration -> Integrating with GRUB -> Yocto project. A user is on either Yocto or Debian, that's why I think it would make it much better to have this as a top level item.
2. Comments on Artifacts section:
- Building Mender image (https://docs.mender.io/development/artifacts/building-mender-image). The header is misspelled ("Buillding" -> "Building")
- Similar to my recommendation above, would rather have two top-level OS sections, i.e. https://docs.mender.io/development/artifacts/yocto-project and https://docs.mender.io/development/artifacts/debian-family. Under there we put what is custom for the OS, including "building" and "image configuration".
- https://docs.mender.io/development/artifacts/image-configuration/debian-family-converted-image-configuration - is this when you convert the image itself? If so I would simply move it to https://docs.mender.io/development/artifacts/building-debian-image. If they want to modify this after the image is built they can simply use the sections https://docs.mender.io/development/artifacts/modifying-a-disk-image and https://docs.mender.io/development/artifacts/modifying-a-mender-artifact.
- https://docs.mender.io/development/artifacts/building-for-production and https://docs.mender.io/development/artifacts/variables are Yocto Project specific. Would put these under the Yocto Project OS section mentioned above.
3. Browsing quickly through the docs I found this section has Yocto-specific settings, which probably should be moved:
I did not see anything else immediately but we should probably go through all the docs as the final step.
4. The packages are called almost the same on Ubuntu 16.04 (uboot-tools is u-boot-tools):
sudo apt install mtools parted mtd-utils e2fsprogs u-boot-tools pigz