Noetic EOL Post

[kscottz]

The intent with this post is to have a single landing page for current ROS 1 users that we can link to from notifications in ROSCore and in RViz.

See this pull request for more context.

[kscottz]

In situ screenshots

[fujitatomoya]

lgtm, several minor comments.

[tfoote]

lgtm with one suggestion/typo fix

[sloretz]

Thank you Kat! 🚀 I have some high level feedback

Assuming the audience is familiar with ROS 1, and is unfamiliar that ROS 1 is going EOL
Assuming the goal of the page is to teach the audience what they need to do about it

I'd recommend the outline:

• ROS 1 is going EoL (already have this)
• What does EoL mean? (already have this)
• What do I need to do? (new section higher level than ROS 2)
  • Recommended: Migrate to ROS 2
    • Include in this section how ROS 2 has real users, and resources for migrating, and where to get help
  • Other migration options (already have this)
    • Build ROS 1 from source
      • Include in this section how ROS-O has patches to build on newer Ubuntu versions
    • Pay Canonical for ROS ESM

[sloretz]

I would recommend we add a page on bridging to the ROS 1 -> ROS 2 migration guide instead of writing it here

[kscottz]

That could be a tough one.

The suggestion would be to have a page, that only exists in the Humble docs branch, on how to compile Humble on 20.04 with the bridge. I could do that pretty quickly if I had some crib notes or a history dump. Would someone have something like that? Are there any gotchas?

[sloretz]

This is a guide I'm wanting to write, but to unblock this PR I'm good with leaving this section in for now. I will make a PR to replace it with a link when I land the bridging doc.

The suggestion would be to have a page, that only exists in the Humble docs branch, on how to compile Humble on 20.04 with the bridge. I could do that pretty quickly if I had some crib notes or a history dump. Would someone have something like that? Are there any gotchas?

I'm thinking making it not ROS distro specific. In my mind it looks like:

1. Pick the ROS 2 distro you want to use
2. Here's how to compile Noetic and the bridge on newer ubuntu distros
3. If something doesn't work, here's how to grab a patch from ROS O

[kscottz]

This would be for Humble and Jazzy in particular?

I don't have an objection but we probably want a black box warning stating that this is only recommended in the case of migration. Feel free to tag me for a review.

[rhaschke]

Note that ROS-O can be easily installed from binaries next to all active ROS2 releases.
I suggest to replace the sentence with something along the following line:

Due to the operating system constraints for the current active ROS releases (Noetic = Ubuntu 20.04, ROS2 >= Ubuntu 22.04) we suggest installing ROS-One next to ROS2 on a decent Ubuntu distro (instead of building ROS2 from source on Ubuntu 20.04).

[kscottz]

@sloretz I did a second pass, I tried to address some of your feedback. I don't think we want to necessarily push all of this information down into the official migration guides, but I am trying to steer people in that direction. Take a look.

[rhaschke]

I generally approve. But there were a lot of typos, which I suggest to fix.

[kscottz]

Thanks for suggestions @rhaschke. Emacs in Markdown mode is a poor substitution for Google Doc's automatic correction tools.

[kscottz]

Please hold off merging this until I have the other two PRs lined up. The RViz one is near done and I still need to put together the one for roscore but that shouldn't take more than a couple hours.

[rhaschke]

Two of my previous comments were not considered yet.

[rhaschke]

I think you should link information about the current limitations. What is not supported anymore?
What exactly is meant with "a little bit of work" in the next sentence?
This information is crucial to people deciding on a migration process.

[sloretz]

LGTM with nits

[sloretz]

Nit, the other items in the list end with a period instead of a comma.

Suggested change

	* *Users must stop using ROS 1 immediately*,
	* *Users must stop using ROS 1 immediately*.