Code of Conduct - ValocityGlobal/Shelta GitHub Wiki

What if my submission has nothing to do with the User Stories or Bugs outlined in the project?

  • There is a clear vision and road map on the vision we have for Shelta. If your Pull Request introduces something outside of the vision of the project, your submission may be rejected.
  • Please ensure you include clear comments as to why you're submitting a PR if it's not related to any work items envisioned for the project.

What happens if my Pull Requests has comments to resolve?

  • One of the beautiful things about contributing to an open source project is learning from other brilliant minds. Please don't take it personal if there are comments on your submission - any feedback is constructive and should be taken as a learning experience. We would expect you to make comments and suggestions on our contributions if they are helpful/insightful too.

What happens if someone violates the code of conduct?

  • If you believe someone is violating the code of conduct we ask that you report it.
  • If you are unsure whether the incident is a violation, or whether the space where it happened is covered by this Code of Conduct, we encourage you to still report it. We would much rather have a few extra reports where we decide to take no action, rather than miss a report of an actual violation. We do not look negatively on you if we find the incident is not a violation. And knowing about incidents that are not violations, or happen outside our spaces, can also help us to improve the Code of Conduct or the processes surrounding it.
  • All reports will be kept confidential. In some cases we may determine that a public statement will need to be made. If that's the case, the identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise.
  • If you believe anyone is in physical danger, please notify appropriate law enforcement first. If you are unsure what law enforcement agency is appropriate, please include this in your report and we will attempt to notify them.
  • We are all friends here and the whole purpose of this project is to empower and help others. That being said, being a dick will not be tolerated and you will be blocked & reported from the project if your actions are abusive or unprofessional. Please respect everyone in this community.

How can I report a violation?

  • We have an email address set up that is monitored by administrators ([email protected]). When you report a violation please include the GitHub User Name of the person violating the code of conduct, the reason they have been flagged as violating the code and link to the area (if applicable).

What do I include in my violation report?

  • Your contact info (so we can get in touch with you if we need to follow up)
  • Names (real, nicknames, or pseudonyms) of any individuals involved. If there were other witnesses besides you, please try to include them as well.
  • When and where the incident occurred. Please be as specific as possible.
  • Your account of what occurred. If there is a publicly available record (e.g. a mailing list archive or a public IRC logger) please include a link.
  • Any extra context you believe existed for the incident.
  • If you believe this incident is ongoing.
  • Any other information you believe we should have.

Who receives the violation report?

  • All responses to reports of conduct violations will be managed by a Code of Conduct Committee ("the committee") which is comprised of a group of Valocity Employees (which could change in the future depending on the contributor relationships established along the way).

  • The Committee is comprised of Valocity employees that donate their free time to this amazing cause.

How long does it take to hear back from a reported violation?

  • When a report is sent to the committee they will reply to the report to confirm receipt. This reply will be sent within 72 hours, and the committee should strive to respond much quicker than that.

What happens after you file a report?

  • You will receive an email acknowledging receipt.

The working group will meet to review the incident and determine:

  • What happened.
  • Whether this event constitutes a code of conduct violation.
  • Who the bad actor was.
  • Whether this is an ongoing situation, or if there is a threat to anyone's physical safety.
  • If this is determined to be an ongoing incident or a threat to physical safety, the working groups' immediate priority will be to protect everyone involved. This means we may delay an "official" response until we believe that the situation has ended and that everyone is physically safe.

Once the working group has a complete account of the events they will make a decision as to how to response. Responses may include:

  • Nothing (if we determine no violation occurred).
  • A private reprimand from the working group to the individual(s) involved.