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

Create CODE_OF_CONDUCT.md #647

Closed
wants to merge 1 commit into from
Closed

Create CODE_OF_CONDUCT.md #647

wants to merge 1 commit into from

Conversation

mcevoyandy
Copy link

why doesn't MoveIt! have a code of conduct? I think it's essential to promote an all-inclusive and welcoming atmosphere.

Description

added code of conduct from Contributor Covenant

Checklist

  • Required: Code is auto formatted using clang-format
  • Extended the tutorials / documentation, if necessary reference
  • Include a screenshot if changing a GUI
  • Optional: Created tests, which fail without this PR reference
  • Optional: Decide if this should be cherry-picked to other current ROS branches (Indigo, Jade, Kinetic)

You can expect a response from a maintainer within 7 days. If you haven't heard anything by then, feel free to ping the thread. Thank you!

why doesn't MoveIt! have a code of conduct? I think it's essential to promote an all-inclusive and welcoming atmosphere.
Copy link
Member

@davetcoleman davetcoleman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense to me

@gavanderhoorn
Copy link
Member

I think this is an ok idea. I wouldn't call it essential though.

@bmagyar
Copy link
Member

bmagyar commented Oct 17, 2017 via email

@v4hn
Copy link
Contributor

v4hn commented Oct 17, 2017

sigh

To be honest I simply don't care about an explicit COC.
I don't oppose, but I don't particularly approve either.

For a long time the general maxim "be excellent to each other" was good enough for FOSS projects.
In my opinion it still is.

That being said, if we want to merge this file, we will have to talk about it at a maintainer meeting before, because this makes us as maintainers to blame if something goes wrong somewhere in the community.

It would be nice if you could attend the next video meeting @mcevoyandy .

Copy link
Contributor

@v4hn v4hn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be discussed/decided on at a maintainer meeting.

@davetcoleman
Copy link
Member

Good point, lets discuss at a maintainer meeting! I think overall its a good discussion to have and can possibly improve MoveIt!'s legitimacy for securing grant money to fund open source projects

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

Successfully merging this pull request may close these issues.

5 participants