Skip to content

Latest commit

 

History

History
94 lines (68 loc) · 4.55 KB

CONTRIBUTING.md

File metadata and controls

94 lines (68 loc) · 4.55 KB

Contributing

Hello! Interested in contributing to this repository and make RustDaVinci even more awesome? Great! When contributing to this repository, please first discuss the change you wish to make via email, You can refer to the TODO list where most of the tasks, ideas and bugs are located. Testing from the master branch is always appreciated and any issues that is found should be added to the TODO list.

Please note we have a code of conduct, please follow it in all your interactions with the project.

Recommendation

When working on/ testing this repository it is highly recommended that you host a private rust server and include "+server.secure 0" in your .bat file. This allow you to avoid trouble with EAC.

Follow this guide to create your own Rust Dedicated Server.

Pull Request Process

  1. Test it! Ensure that your fix does not break the rest of the code.
  2. Update the TODO list and possibly the README file with necessary information about the changes you've made. Things such as Changes to the interface, new modules used should update the setup.py and requirements.txt, new files etc...
  3. When you are satisfied with the fix go ahead rebase & squash your commits and create a Pull Request.
  4. Once the Pull Request has been reviewed and accepted, maintainer will merge it into the master branch.

Code of Conduct

Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

Our Standards

Examples of behavior that contributes to creating a positive environment include:

  • Using welcoming and inclusive language
  • Being respectful of differing viewpoints and experiences
  • Gracefully accepting constructive criticism
  • Focusing on what is best for the community
  • Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

  • The use of sexualized language or imagery and unwelcome sexual attention or advances
  • Trolling, insulting/derogatory comments, and personal or political attacks
  • Public or private harassment
  • Publishing others' private information, such as a physical or electronic address, without explicit permission
  • Other conduct which could reasonably be considered inappropriate in a professional setting

Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

Scope

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [[email protected]]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at http://contributor-covenant.org/version/1/4