Skip to content

Latest commit

 

History

History
81 lines (63 loc) · 4.47 KB

CONTRIBUTING.md

File metadata and controls

81 lines (63 loc) · 4.47 KB
Raw

How to contribute to avocado

Thank you for sharing your code with the avocado project. We appreciate your contribution!

Join the mailing list and our IRC channel

If you're not already on the avocado developers list, take a minute to join. It would be great if you'd introduce yourself to the group but it's not required. You can just let your code do the talking for you if you like.

You can find us on Freenode IRC in the #adamdev room.

Check the issue tracker

Before you write too much code, check the open issues in the avocado issue tracker to see if someone else has already filed an issue related to your work or is already working on it. If not, go ahead and open a new issue.

Announce your work on the mailing list

Shoot us a quick email on the mailing list letting us know what you're working on. There will likely be people on the list who can give you tips about where to find relevant source or alert you to other planned changes that might effect your work.

If the work you're proposing makes substantive changes to avocado, you may be asked to attach a design document to your issue in the issue tracker. This document should provide a high-level explanation of your design, clearly define the goal of the new design and explain the expected effects on performance, APIs, etc. This document is meant to save you time as it allows the team a chance to provide feedback on the proposes changes. It's likely we can help you find a way to achieve your goals with less work. The document also allows the team to prepare for large changes to the code base. We welcome change but also want to ensure that code quality is kept high.

Submit your pull request

Github provides a nice overview on how to create a pull request.

Some general rules to follow:

  • Do your work in a fork of the avocado repo.
  • Create a branch for each feature/bug in avocado that you're working on. These branches are often called "feature" or "topic" branches.
  • Use your feature branch in the pull request. Any changes that you push to your feature branch will automatically be shown in the pull request.
  • If your pull request fixes an issue, reference the issue so that it will be closed when your pull request is merged
  • Keep your pull requests as small as possible. Large pull requests are hard to review. Try to break up your changes into self-contained and incremental pull requests, if need be, and reference dependent pull requests, e.g. "This pull request builds on request #92. Please review #92 first."
  • The first line of commit messages should be a short (<80 character) summary, followed by an empty line and then, optionally, any details that you want to share about the commit.
  • Include unit tests with your pull request. We love tests and use Jenkins to check every pull request and commit. Just look for files in the avocado repo that end in "*Suite.scala", e.g. avocadoContextSuite.scala, to see examples of how to write tests.
  • Please try to follow the existing coding style. Sources can be automatically formated by running "mvn process-sources".
  • Make sure to add a copyright header to all new files (see below).

Update CHANGES.md file

  • The CHANGES.md file is updated to indicate changes that are resolved for the next release. Please update the file with your commit.

Copyright header and Licensing

avocado is released under the Apache License, Version 2.0. Any new files added need to have a header with a license like the following, e.g.

''' /**

  • Copyright (c) [year]. [insert your company or name here]
  • Licensed under the Apache License, Version 2.0 (the "License");
  • you may not use this file except in compliance with the License.
  • You may obtain a copy of the License at
  • http://www.apache.org/licenses/LICENSE-2.0
  • Unless required by applicable law or agreed to in writing, software
  • distributed under the License is distributed on an "AS IS" BASIS,
  • WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  • See the License for the specific language governing permissions and
  • limitations under the License. */ '''