Skip to content

Latest commit

 

History

History
70 lines (52 loc) · 3.11 KB

CONTRIBUTING.md

File metadata and controls

70 lines (52 loc) · 3.11 KB
Raw

How to Contribute to Eclipse Kanto

First of all, thanks for considering to contribute to Eclipse Kanto. We really appreciate the time and effort you want to spend helping to improve things around here.

In order to get you started as fast as possible we need to go through some organizational issues first, though.

Eclipse Contributor Agreement

Before your contribution can be accepted by the project team contributors must electronically sign the Eclipse Contributor Agreement (ECA).

Commits that are provided by non-committers must have a Signed-off-by field in the footer indicating that the author is aware of the terms by which the contribution has been provided to the project. The non-committer must additionally have an Eclipse Foundation account and must have a signed Eclipse Contributor Agreement (ECA) on file.

For more information, please see the Eclipse Committer Handbook: https://www.eclipse.org/projects/handbook/#resources-commit

Code Style Guide

  • Keep the code well-formatted through: gofmt
  • Keep the code error-free through: go vet and golint
  • Avoid common mistakes and pitfalls following: Go Code Review Comments

Making Your Changes

  • Fork the repository on GitHub.
  • Create a new branch for your changes.
  • Make your changes following the code style guide (see Code Style Guide section above).
  • When you create new files make sure you include a proper license header at the top of the file (see License Header section below).
  • Make sure you include test cases for non-trivial features.
  • Make sure test cases provide sufficient code coverage (see GitHub actions for minimal accepted coverage).
  • Make sure the test suite passes after your changes.
  • Commit your changes into that branch.
  • Use descriptive and meaningful commit messages. Start the first line of the commit message with the issue number and titile e.g. [#9865] Add token based authentication.
  • Squash multiple commits that are related to each other semantically into a single one.
  • Make sure you use the -s flag when committing as explained above.
  • Push your changes to your branch in your forked repository.

License Header

Please make sure any file you newly create contains a proper license header like this:

Adjusted for Go files:

// Copyright (c) {year} Contributors to the Eclipse Foundation
//
// See the NOTICE file(s) distributed with this work for additional
// information regarding copyright ownership.
//
// This program and the accompanying materials are made available under the
// terms of the Eclipse Public License 2.0 which is available at
// https://www.eclipse.org/legal/epl-2.0, or the Apache License, Version 2.0
// which is available at https://www.apache.org/licenses/LICENSE-2.0.
//
// SPDX-License-Identifier: EPL-2.0 OR Apache-2.0

Submitting the Changes

Submit a pull request via the normal GitHub UI.

After Submitting

  • Do not use your branch for any other development, otherwise further changes that you make will be visible in the PR.