The renaming of the repositories autoware.universe and autoware.core

[youtalk]

The migration from autoware.universe to autoware.core is progressing, and the completion of the first phase is approaching.
https://github.com/orgs/autowarefoundation/discussions/5365
Thank you for all of your contribution @mitsudome-r and AWF members.

I'm considering releasing autoware.core through the ROS build farm, and as part of this, I would like to rename the repository to autoware_core to align with ROS naming conventions. Does anyone have any objections to this?

As the final step of the migration to autoware_core, we plan to create a metapackage named autoware_core. This will allow all necessary packages for autoware_core to be installed via apt get install ros-$ROS_DISTRO-autoware-core.
Therefore, the repository name autoware_core would be more consistent than autoware.core.

To rename autoware.core, we are also considering renaming autoware.universe to autoware_universe for consistency.

With the GitHub forwarding feature, existing cloned repositories should not be affected.

[xmfcx]

By the way, yesterday I was looking at the autoware.repos repositores with blank eyes and thinking, how annoying "autoware.universe" and "autoware.core" has different delimiters than everything else.

#	Repository Name	Directory
1	autoware_msgs	core/autoware_msgs
2	autoware_adapi_msgs	core/autoware_adapi_msgs
3	autoware_internal_msgs	core/autoware_internal_msgs
4	autoware_cmake	core/autoware_cmake
5	autoware_utils	core/autoware_utils
6	autoware_lanelet2_extension	core/autoware_lanelet2_extension
7	autoware.core	core/autoware.core
8	autoware.universe	universe/autoware.universe
9	tier4_ad_api_adaptor	universe/external/tier4_ad_api_adaptor
10	tier4_autoware_msgs	universe/external/tier4_autoware_msgs
11	morai_msgs	universe/external/morai_msgs
12	muSSP	universe/external/muSSP
13	pointcloud_to_laserscan	universe/external/pointcloud_to_laserscan
14	eagleye	universe/external/eagleye
15	rtklib_ros_bridge	universe/external/rtklib_ros_bridge
16	llh_converter	universe/external/llh_converter
17	glog	universe/external/glog
18	autoware_launch	launcher/autoware_launch
19	sensor_component_description	sensor_component/external/sensor_component_description
20	tamagawa_imu_driver	sensor_component/external/tamagawa_imu_driver
21	nebula	sensor_component/external/nebula
22	transport_drivers	sensor_component/transport_drivers
23	ros2_socketcan	sensor_component/ros2_socketcan
24	sample_sensor_kit_launch	sensor_kit/sample_sensor_kit_launch
25	awsim_sensor_kit_launch	sensor_kit/external/awsim_sensor_kit_launch
26	awsim_labs_sensor_kit_launch	sensor_kit/awsim_labs_sensor_kit_launch
27	single_lidar_sensor_kit_launch	sensor_kit/single_lidar_sensor_kit_launch
28	sample_vehicle_launch	vehicle/sample_vehicle_launch
29	awsim_labs_vehicle_launch	vehicle/awsim_labs_vehicle_launch
30	pacmod_interface	vehicle/external/pacmod_interface
31	autoware_individual_params	param/autoware_individual_params

[youtalk]

Yeah, it's time to standardize the naming convention!

[Timple]

Curious: What would be the benefit of a meta package?

If a tutorial starts with ros2 launch some_autoware_package some_launchfile, it should be enough to install some_autoware_package as it should contain all dependencies.

[mitsudome-r]

Having a meta-package would group all the autoware related packages and enables the users to install with one command e.g. "sudo apt install ros-humble-autoware-core". There could be multiple launch packages that can be used for autoware and users won't have to install them one by one.

[esteve]

@youtalk sounds good to me, thanks for all the work 🙂

I also agree on the metapackage, it'd make it much easier for users to install Autoware.core in one step. Let me know if I can help with that

[mitsudome-r]

As discussed in the Software WG meetings, I have renmaed the autoware.universe and autoware.core repositories