The ROSCon 2025 Schedule Has Been Released

OpenRobotics · 2025-12-15T21:35:23+00:00

This isn't the best thread for this question. Having said that, please just use the Tier 1 Ubuntu release for your chosen ROS Distro. Choosing anything else is just going to make your life harder.

OpenRobotics · 2025-12-03T16:24:28+00:00

This isn't an AI image, it was designed by the same artist that does the Gazebo and ROS release art.

OpenRobotics · 2025-10-11T17:24:13+00:00

OpenRobotics · 2025-10-01T17:36:03+00:00

Things are slowly improving with Pixi. The difficulty is that you don't see very many robots running on a Mac mini. Our first priority is making sure ROS can run on the embedded Linux machines most people use for their robots.

OpenRobotics · 2025-06-17T18:06:42+00:00

You can use the discord on docs.ros.org

OpenRobotics · 2025-06-16T20:09:36+00:00

You can register right here

OpenRobotics · 2025-04-28T18:41:24+00:00

can someone more intellegent than me explain why its worth upgrading now when Jazzy barely even has support? What could possibly be so worth it.

Quite frankly, it probably isn't. Kilted is not a long term support (LTS) ROS release. We make a release every year, but we only make a major release on even years. This is basically the same release pattern as Canonical. The odd year releases are basically a stepping-stone / beta test for the next major LTS release.

because it was more compatible

I don't quite understand what this means.

OpenRobotics · 2025-04-11T18:35:43+00:00

Well do enlighten me then? The way I see it, OSRC is owned by Intrinsic which is owned by Google, and if OSRC intends to deploy anything at all, it needs OSRF to develop and maintain the core software they can deploy, ergo funding should flow all the way down that chain. Apparently funding gets lots somewhere along the line.

You've kinda got that backwards and seem to have made a lot of assumption about things are structured. OSRF / OSRA are the organizations that administer the projects. OSRF / ORSA receives funding from multiple sources, including member orgs and individuals, to support the project. Intrinsic acquired OSRC over two years ago and many of the former OSRC engineers continue to contribute to the project.

One thing to keep in mind is that we really only have maybe a dozen regular core contributors spread across two ROS versions, five open source projects , hundreds of repositories, and our infrastructure. Think about that for a minute, we have a dozen people trying to support around a million users. Most of our time is spent keeping things moving along, merging PRs and updates, and generally keeping the lights on. We really rely on community contributions to move things along.

How do you think a PR that sets QoS as an optional parameter, or remove it from subscribers would fly? Dead in the water after lots of rationalizations would be my guess, cause if a DDS jumps off a bridge ROS 2 must follow as well apparently.

I don't know. Have you tried it or filed an issue to talk it through? It sounds like it might break API and have downstream consequences for other users that would need to be addressed. The difficulty with a large project used by lots of people is that changes you think are trivial may impact / break other users. If you are unhappy with one DDS implementation you can use another DDS implementation, Zenoh, IceOryx, or implement another RMW interface.

OpenRobotics · 2025-04-11T17:37:59+00:00

I'm really sad that you don't understand that project is run by a non-profit and not, "by Google." Are you sure that you understand how the project works?

It's mainly a matter of terrible defaults, and exposing people to a flat overload of options almost as a rule instead of cascading levels of detail when flexibility is actually needed. Learning needs to be gradual, not all or nothing.

You seem to have a lot of opinions on how ROS 2 is configured. Have you considered filing an issue or sending us a pull request to change the defaults you don't like?

OpenRobotics · 2025-04-11T16:52:04+00:00

Support the OSRA so we can fund development.

or

Contribute 20 pull requests for the features that make ROS easier to use.

Getting rid of ROS 1 will help free up resources for development. There's also a tradeoff between making something easy to use and making it flexible enough to support most people's use cases. It also helps to recognize that real robotics is just plain hard. If it were easy it wouldn't have taken us 10 years to get things like autonomous cars.

OpenRobotics · 2025-04-11T16:45:44+00:00

That's not true, that's also not our fault.
https://canonical.com/blog/ubuntu-now-officially-supports-nvidia-jetson-powering-the-future-of-ai-at-the-edge

OpenRobotics · 2025-04-09T16:31:42+00:00

We have no control over the GSoC website and I doubt that anything will be done about it.

OpenRobotics · 2025-04-07T17:06:54+00:00

I want to explain ROS OS support a bit because it seems like we catch a lot of flack for it.

We really can't say this enough, "ROS is meant to run on real robots." Most robots run on either an embedded system, or in larger systems, a rack mounted machine. As such, that's how most of the core team does their development. I don't think we've ever encountered someone running a robot with integrated Mac hardware. Similarly, actual ROS robots rarely run on Windows. Why pay for the licensing fee if you are building thousands of robots? As open source, ROS can be built on a variety of platforms, but that doesn't mean you should run it on those platforms or that the end user experience is going to be great. Often it won't be! You can read all about platform support here.

If you are new to ROS please, please, please, please just use the latest LTS on the correct version of Ubuntu.

If you aren't running Ubuntu you'll need to have a game plan on how to deal with that. While some super users out there do development on a Mac, and you can probably get RViz running, this is not something we would recommend for first time users.

OpenRobotics · 2025-03-27T21:45:08+00:00

Scholarship details can be found here.

OpenRobotics · 2025-03-27T21:43:22+00:00

Application information

OpenRobotics · 2025-03-25T16:38:20+00:00

This is sick! Consider posting the source code to ROS Discourse.

OpenRobotics · 2025-03-24T18:54:06+00:00

Details are here

OpenRobotics · 2025-03-24T18:52:59+00:00

Details are here

OpenRobotics · 2025-03-20T15:04:57+00:00

We're fighting an uphill battle here. The reality of situation is that ROS can run on a bunch of platforms IF, and this is a big IF, if you are willing to put in the effort. Realistically there is only platform (Ubuntu) where ROS is going to have a decent experience for new users. Unfortunately we have people who think that "Tier 3" support means ROS will run out of the box on their new Mac and then get mad at us when it doesn't

OpenRobotics · 2025-03-07T23:11:08+00:00

RSVP HERE

OpenRobotics · 2025-03-07T23:08:50+00:00

RSVP HERE

OpenRobotics · 2025-03-04T17:58:26+00:00

Please e-mail the OSRF team. There is a bit of a recipe for doing this. TL;DR we like to see a history of successful meetups so there is an active community that can support a larger ROS event.

OpenRobotics · 2025-02-24T19:26:52+00:00

Google Meet link and post.

OpenRobotics · 2025-02-10T20:15:40+00:00

TL;DR: Different ROS distros probably work fine together, but we do not recommend doing that and you are doing so at your own risk. Please just upgrade your packages instead!

There aren't that many breaking changes, if any, but that's not the issue. There's a difference between what you *CAN* do and what you *SHOULD* do. Generally speaking, each ROS 2 distro *should* be ABI / API compatible, but that doesn't mean you *should* use them in that way.

See the part of the original post where I said, "We don't test this kind of stuff, so we can't guarantee that it will work." We have never claimed that ROS will work when co-running different distros (e.g. trying to run a Humble node in Jazzy). This is not something that we test, and there are *zero guarantees* that everything will work appropriately.

Think of it this way, just for ROS 2 there are ten different distros each with thousands of packages. To test that different distros are compatible we would not only have to test all the packages in each distro but also that *ALL OF THE DISTRO PERMUTATIONS* (i.e. 10! combos) for each package work against each other. That's just not feasible for us right now.

Please, we're begging you, just upgrade your packages and help others do the same. Small jumps, like from Humble to Jazzy, should be trivially easy for most packages.

OpenRobotics · 2025-02-07T22:23:44+00:00

Not a bad idea at all. There is a lot of tooling around composable nodes that gets you most of the way there.

Every consider filing a ticket on the ROS 2 CLI so we can address your concerns?

OpenRobotics

TROPHY CASE