Skip to content

Latest commit

 

History

History
141 lines (104 loc) · 7.83 KB

CONTRIBUTING.md

File metadata and controls

141 lines (104 loc) · 7.83 KB
Raw

Contributing to Liquid Prep

Liquid Prep is an open source project and always welcome contributions to the project. You can contribute in the following ways:

  • Software and Hardware testing
  • Localization and improvisation of the application
  • Add/Update crop data
  • Enhance watering advise agorithm
  • Pilot testing the solution
  • Improve the documentation
  • Report bug and/or work on existing issues
  • Request/recommend new features in our issues or discussions board

Please read our contributing guidelines.

Technical Steering Committee (TSC)

The TSC will be responsible for all technical oversight of the Liquid Prep project. Participation in the Project through becoming a Contributor and Committer is open to anyone.

The TSC may

  1. Establish work flow procedures for the submission, approval, and closure/archiving of projects
  2. Set requirements for the promotion of Contributors to Committer status, as applicable
  3. Amend, adjust, refine and/or eliminate the roles of Contributors, and Committers, and create new roles, and publicly document any TSC roles, as it sees fit.

Responsibilities

The TSC will be responsible for all aspects of oversight relating to the Project, which may include:

  • Coordinating the technical direction of the Project.
  • Approving project or system proposals (including, but not limited to, incubation, deprecation, and changes to a sub-project’s scope).
  • Organizing sub-projects and removing sub-projects.
  • Creating sub-committees or working groups to focus on cross-project technical issues and requirements.
  • Appointing representatives to work with other open source or open standards communities.
  • Establishing community norms, workflows, issuing releases, and security issue reporting policies.
  • Approving and implementing policies and processes for contributing.

The TSC voting members are initially the Project’s Committers. At the inception of the project, the Committers of the Project will be as set forth within the “CONTRIBUTING” file within the Project’s code repository. The TSC may choose an alternative approach for determining the voting members of the TSC, and any such alternative approach will be documented in this CONTRIBUTING file. Any meetings of the Technical Steering Committee are intended to be open to the public, and can be conducted electronically, via teleconference, or in person.

TSC Voting

While the Project aims to operate as a consensus-based community, if any TSC decision requires a vote to move the Project forward, the voting members of the TSC will vote on a one vote per voting member basis.

Quorum for TSC meetings requires at least fifty percent of all voting members of the TSC to be present. The TSC may continue to meet if quorum is not met but will be prevented from making any decisions at the meeting.

Current TSC members

Contributing Guidelines

When contributing a major change to this repository, please first discuss the change you wish to make via an issue or via Slack in the #liquid-prep channel. Minor issues can simply be addressed by sending by a pull request.

All pull requests will require you to ensure the change is certified via the Developer Certificate of Origin (DCO). The DCO is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project.

Please note we have a Code of Conduct, please follow it in all your interactions with the project and its community.

Pull request process

  1. Fork the repository.
  2. Commit your changes to your fork.
  3. Submit a pull request.
  4. Handle any feedback before the request is merged.
  5. Accept our sincere Thank You!

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 on Slack in the #liquid-prep channel or send an email to [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