privacy_msgs: 1.1.0-1 in 'humble/distribution.yaml' [bloom]

[severin-lemaignan]

Increasing version of package(s) in repository privacy_msgs to 1.1.0-1:

• upstream repository: https://github.com/ros4hri/privacy_msgs.git
• release repository: https://github.com/ros4hri/privacy_msgs-release.git
• distro file: humble/distribution.yaml
• bloom version: 0.10.7
• previous version for package: null

privacy_msgs

1.1.0 (2024-09-16)
------------------
* {privacy_centre -> privacy_msgs}
* [doc] cleanup README
* Contributors: Séverin Lemaignan

1.0.0 (2024-02-16)
------------------
* {SensitiveData->PersonalDataProcessor}
* initial commit of privacy_msgs
* Contributors: Séverin Lemaignan

[sloretz]

Holding for Humble sync

[nuclearsandwich]

@severin-lemaignan can we move this release repository to ros2-gbp?

I can start the PR and mirroring process to add it to the ros4hri team: https://github.com/ros2-gbp/ros2-gbp-github-org/blob/latest/ros4hri.tf

[severin-lemaignan]

yes please! (sorry, I always forget how the ros2-gbp process work. It is certainly documented somewhere, but I just don't seem to have the required mental bandwidth to handle it properly 😔)

[nuclearsandwich]

An additional note after taking a moment to do full review. I don't think this meets REP-144 criteria. privacy_msgs is insufficiently scoped. I think hri_privacy_msgs could be an alternative.

[tfoote]

This looks a little bit too generic for a REP 144 package naming standards. https://www.ros.org/reps/rep-0144.html

This looks to have one message which is very application specific. Which doesn't justify claiming the name privacy for the whole ROS ecosystem.

Please use a name that explains the scope of where this package is expected to be reused in a prefix otherwise making the name more specific. Possibly the privacy standard that it's targeted for, or the project that it's going to be used for.

[severin-lemaignan]

thanks for the feedback. I'll revise accordingly.

[github-actions]

This PR hasn't been activity in 14 days. If you are still are interested in getting it merged please provide an update. Otherwise it will likely be closed by a rosdistro maintainer following our contributing policy. It's been labeled "stale" for visibility to the maintainers. If this label isn't appropriate, you can ask a maintainer to remove the label and add the 'persistent' label.