Comments (2)
Thanks for creating the issue.
Although this would help a lot of ROS users, I would like to think carefully about the timing and the target package.
I propose to do this after we do a clean up of messages (replacing autoware_auto_msgs with autoware_msgs). This is because change in interface could be quite a disruptive change and we would like to have more organized interface before making it ROS "official" release.
Also, I think we should only release into the ROS buildfarm for the packages in Core considering the fact that we defined Core as AWF maintained package and Universe to be community maintained. Universe packages can be registered to ROS buildfarm by the owner of the package at their decision. As Core is currently empty, we should start with porting Universe packages into Core first before doing this task.
from autoware.
Although this would help a lot of ROS users, I would like to think carefully about the timing and the target package.
Absolutely! This issue is just meant to start the discussion and find out what steps we'd need if we ever want to release Autoware into the ROS buildfarm, but I don't think we're ready now to do it.
I propose to do this after we do a clean up of messages (replacing autoware_auto_msgs with autoware_msgs). This is because change in interface could be quite a disruptive change and we would like to have more organized interface before making it ROS "official" release.
Sounds good. I found autowarefoundation/autoware_msgs#2 and I can work on it, if nobody else is working.
Also, I think we should only release into the ROS buildfarm for the packages in Core considering the fact that we defined Core as AWF maintained package and Universe to be community maintained. Universe packages can be registered to ROS buildfarm by the owner of the package at their decision. As Core is currently empty, we should start with porting Universe packages into Core first before doing this task.
A priori I don't see the problem with releasing Autoware.Universe as well, but I understand that Autoware.Core is meant to be of higher quality, so it might make sense releasing it first.
However, the way package releases work with the ROS buildfarm is that bloom releases all the packages in a given repository (that's why it's required that all packages have the same version in their package.xml
). So if we want to let community maintainers to release their packages on their own, they'll have to keep the packages in separate repositories and not all in Autoware.Universe. If anyone runs bloom
on the Autoware.Universe repository, they'll release all the packages there.
from autoware.
Related Issues (20)
- Docker build script fails with error `invalid not-modified ETag` HOT 7
- `docker/build.sh` should ignore the cache HOT 1
- Logging simulator not showing surrounding enviroment updates with Rosbag replay using docker HOT 1
- Handle invalid areas / lanelets HOT 1
- heaphook: roadmap to stable debian package HOT 1
- Maintenance of awsim_sensor_kit calibration files for using the latest autoware universe HOT 1
- PluginlibFactory: The plugin for class 'autoware_rviz_debug/DecisionMakerPanel' failed to load. HOT 3
- Move drivers into separate .repos file HOT 6
- .
- [points2image]Looks like camera_info or projection_matrix are not being published.. Please check that both are running.. HOT 2
- Add routing interface HOT 2
- Double detection of objects
- Set up AWS EC2 instance for generating Debian packages nightly HOT 3
- DevOps Dojo: Developer - VS Code Settings (Parameter JSON Schema and YAML)
- Add option to lanelet2_map_loader for local coordinates HOT 5
- Replace binary images with lighter SVG counterparts HOT 11
- Clean unused dependencies to improve build time HOT 7
- Create API to request manual operation HOT 5
- Lanelet misplaced in Autoware HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from autoware.