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

remove master/slave references #151

Open
trusktr opened this issue Jun 18, 2020 · 4 comments
Open

remove master/slave references #151

trusktr opened this issue Jun 18, 2020 · 4 comments

Comments

@trusktr
Copy link

trusktr commented Jun 18, 2020

It will be more respectful for all possible users to remove the master / slave terminology from the lib.

let MasterApiClient = require('./MasterApiClient.js');
let SlaveApiClient = require('./SlaveApiClient.js');

PR with initial replacements: #152. I'm not sure what will break yet.

@chfritz
Copy link
Contributor

chfritz commented Jun 18, 2020

Would it make sense to wait and see how ROS core decides to resolve this issue first? I think it would be very confusing to use different terminology in the ROS libraries than in ROS core.

@trusktr
Copy link
Author

trusktr commented Jun 18, 2020

I have a feeling it will take more time for ROS core, because it may be a huge breaking change. Do you know if there's interest there?

@chfritz
Copy link
Contributor

chfritz commented Jun 18, 2020

No, I haven't spoken with anyone at OSRF lately. I agree though that is could end up being a huge change. It might even require every ROS user to update their code, since the words in question appear in the API itself.

@chris-smith
Copy link
Collaborator

I think I'd at least like to hear what ROS thinks. Doing this would break the api and make it harder for new and current users.

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

3 participants