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

AeroVironment MacCready Works REP-144 Name Prefix of "avmw_" #39863

Open
Ryanf55 opened this issue Feb 9, 2024 · 1 comment
Open

AeroVironment MacCready Works REP-144 Name Prefix of "avmw_" #39863

Ryanf55 opened this issue Feb 9, 2024 · 1 comment

Comments

@Ryanf55
Copy link
Contributor

Ryanf55 commented Feb 9, 2024

I would like to "reserve" a REP-144 complaint name prefix for AeroVironment MacCready Works. We don't yet have any packages published, but the engineers in my division have an interest to contribute open source on things that would benefit the ROS community that aren't tied to any of our intellectual property.

Can we reserve a name prefix in rosdistro while we work on our packages internally so it doesn't get scooped from under us? The effect of getting scooped results in an ABI breaking change in many internal repos in the CMake target names and namespaces for all the code, which would be unfortunate, time-consuming, and costly for my team to have to deal with.

I propose the following name prefix:
avmw_ = AeroVironment MacCready Works

avmw is not yet taken: https://github.com/search?q=repo%3Aros%2Frosdistro%20avmw&type=code

If this name is accepted, how could we go about reserving the prefix?

@Ryanf55 Ryanf55 changed the title AeroVironment MacCready Works REP-144 Name Prefix of "avmw_` AeroVironment MacCready Works REP-144 Name Prefix of "avmw_" Feb 9, 2024
@clalancette
Copy link
Contributor

First of all, thank you for checking in about the names. This will ensure that the names already meet REP-144. From that perspective, the avmw_ prefix for the packages seems fine.

As far as reserving it, we have no policies or procedures for doing that, and I really don't want to start. At least for now, the community is small enough that I don't think it is warranted.

What I can suggest is that as soon as you have the packages ready, you open up PRs that at least add in the source entries for these packages. That will at least ensure that you start using the names as soon as they are ready.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants