Skip to content

Latest commit

 

History

History
63 lines (46 loc) · 2.36 KB

CONTRIBUTING.md

File metadata and controls

63 lines (46 loc) · 2.36 KB

Contributing to Enphase Open Source Projects

👍🎉 First off, thanks for taking the time to contribute! 🎉👍

All Enphase projects adhere to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected].

The following is a set of guidelines for contributing to Enphase Open Source Projects. These are just guidelines, not rules, use your best judgment and feel free to propose changes to this document in a pull request.

[Issues]

Issues are created here.

  • [How to Contribute in Issues]
  • [Asking for General Help]
  • [Submitting a Bug Report]
  • [Triaging a Bug Report]
  • [Resolving a Bug Report]

Languages

We accept issues in any language. When an issue is posted in a language besides English, it is acceptable and encouraged to post an English-translated copy as a reply. Anyone may post the translated reply. In most cases, a quick pass through translation software is sufficient. Having the original text as well as the translation can help mitigate translation errors.

Responses to posted issues may or may not be in the original language.

Please note that using non-English as an attempt to circumvent our Code of Conduct will be an immediate, and possibly indefinite, ban from the project.

Pull Requests

Pull Requests are the way concrete changes are made to the code, documentation, dependencies, and tools contained in the electron/electron repository.

  • [Setting up your local environment]
    • [Step 1: Fork]
    • [Step 2: Build]
    • [Step 3: Branch]
  • [Making Changes]
    • [Step 4: Code]
    • [Step 5: Commit]
      • [Commit message guidelines]
    • [Step 6: Rebase]
    • [Step 7: Test]
    • [Step 8: Push]
    • [Step 9: Opening the Pull Request]
    • [Step 10: Discuss and Update]
      • [Approval and Request Changes Workflow]
    • [Step 11: Landing]
    • [Continuous Integration Testing]

Style Guides

See [Coding Style] for information about which standards Enphase adheres to for various programming languages.

Licensing

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as specified in our [License Policy], without any additional terms or conditions.