Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add an Astrobee demo #130

Open
mkhansenbot opened this issue Jan 30, 2024 · 3 comments
Open

Add an Astrobee demo #130

mkhansenbot opened this issue Jan 30, 2024 · 3 comments

Comments

@mkhansenbot
Copy link
Contributor

An Astrobee simulation already exists based on ROS. We'd need to port to ROS 2 and build it as part of our demos.

@mkhansenbot mkhansenbot added this to the humble-2024.04.0 milestone Jan 30, 2024
@mkhansenbot
Copy link
Contributor Author

Added to next milestone (proposed) humble-2024.04.0

@Bckempa
Copy link
Contributor

Bckempa commented Jan 30, 2024

An astrobee port to ros2 in already in-progress upstream which should speed this up: https://github.com/nasa/astrobee/tree/ros2

@ivanperez-keera
Copy link
Contributor

I'd like to propose that we put ideas elsewhere (discussions?) until we agree on "attacking" them. If we use the issues as a brainstorming/idea area, it's going to be super hard for people to know what we are really working on, for us to know what we are really working on, for us to plan each milestone, and for us to know what is broken vs what would be a nice to have.

That's not to say this is not important, it's just a way to manage complexity and facilitate focus. Nothing else.

Over the years, IKOS fell into a similar trap, and we now have issues that cannot be closed because it's not like we will absolutely never ever do anything about them, but they cannot be completed because we don't have the resources. As a result, they just stale indefinitely (the oldest is currently 6 years old; I'm currently trying to solve the problem in IKOS too, but that's a separate story). I've seen projects where this continues growing and gets well into the thousands. It just makes the project absolutely unmanageable in the long term.

To go one step further, I'd propose that, after each release, we open a thread under discussions called "what to work on for release 2024.04.0" (or whichever it is). See, for example: NASA-SW-VnV/ikos#258.

@ivanperez-keera ivanperez-keera removed this from the humble-2024.04.0 milestone Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

3 participants