Skip to content
This repository was archived by the owner on Oct 30, 2019. It is now read-only.

Contribution Guidelines

Jump to bottom
brian-murray35 edited this page Aug 19, 2015 · 79 revisions

BUILD is composed of multiple modules, each of which have their own repository. This document describes how to make contributions to any of these modules.

We want to make it simple and rewarding to contribute to BUILD based on the following principles:

  • As easy and transparent as possible to contribute.
  • Free, permanent, and public availability of the most up-to-date code base.
  • On-going maintenance and enhancement under a collaborative software development model.
  • High quality, consistent product performance and usability.
  • Commercial-friendly, mutually-assuring, standard license agreements.
  • Faithful adherence to evolving BUILD coding standards.
  • Respectful, honest, and technically-oriented communications throughout.
  • Security as the number one priority.

##What to Contribute?

You might know what you want to do. Otherwise consider contributing to BUILD in one or all of the following ways:

  • Contribute Bug Reports - contribute by reporting bugs you encountered when using Project BUILD. When you report a bug, a code reviewer/committer on the core development team reviews it, approves it as a real bug, asks you for for more details, or closes it. Approved bugs are either assigned to a committer in GitHub to fix or added to the backlog for future resolution. All bugs remain open until they are fixed. A bug that is about a real bug is closed as soon as the fix is committed. The closing comment explains which version(s) contain the fix. You can report bugs, or review and have conversations with other contributors about existing issues with the Bug label. Click here for more information.

  • Contribute Bug Fixes - you can contribute by fixing bugs. Simply browse the GitHub Issue Tracker for the relevant sub-project, and identify a bug with the label Please Contribute you want to fix. Before you begin, make sure that it is reproducible in the latest version of the sub-project, and has not already been fixed. For instructions on how to submit a pull request to include your bug fix in the latest version of the relevant module, see Changing Code and Submitting Your Changes below.

  • Contribute Enhancements and Optimizations - you can contribute new features or enhancements, or contribute to already scheduled new features (with the label Please Contribute) in the sub-project GitHub Issue Tracker. Project Norman welcomes optimizations, new features and enhancements to existing features. However, we do not accept all feature requests. Therefore, to ensure that you are spending your time wisely, prior to coding your proposed enhancements we request that propose and discuss new features to core project developer first by creating an Issue labelled Feature Enhancement in the relevant sub-project GitHub Issue Tracker. For more information on proposing new features using the GitHub Issue Tracker of the relevant sub-project, see Using The [](GitHub Issue Tracker). When a core developer responds, discuss the proposed enhancement with them. Once this discussion yields a shared consensus, you can confidently proceed and create the code. Furthermore, the developer might have some valuable hints and tips that save you a lot of time of and effort.However, before you do any work beyond conceptual, we recommend you post an Issue with the label User Story on the GitHub Issue Tracker. When a core developer contacts you, discuss the proposed enhancement with them. For instructions on how to submit a pull request to include your bug fix in the latest version of the relevant module, see Changing Code and Submitting Your Changes below.

  • Provide Miscellaneous Information - inevitably, there is a wealth of information which the community would benefit from but that nobody has yet provided. We welcome contributions of all types of project-information, such as test scenarios and results in various environments, performance tests and results, How To or API documentation, and any other information you think the community will be able to use. Check the bugs in the GitHub Issue Tracker in the BUILD module you interested in contributing to. You might be able to provide further information, or a hint that helps other contributors understand the bug. Click here for more information.

  • ###Assist other users - you can contribute to BUILD by helping others users who need support. You can check SAP Community Network (SCN) for support requests, or review issues in the issue tracker. Click here for more information.

#Changing Code and Submitting Your Changes

Use the following procedure to change code, whether it is a bug fix or a new feature, and submit your changes:

  1. Review the [Apache License] which outlines both your and the BUILD Open Source Community's legal rights regarding your contribution.

  2. Download, read, sign, and send us our Individual Contribution License Agreement if you want to submit code as an individual. Alternatively, if you want to submit code on behalf of your employer, a company representative authorized to do so needs to download, fill, and print the Corporate Contributor License Agreement form.

  3. Fork the module. For more information, see Fork a Repo.

  4. Install the required dependencies and tools.

  5. Implement your new feature or bug fix on your branch, taking the following into consideration:

  • Base all your work off of the master branch.
  • Please name your branch to match the new feature of bug fix that you are submitting.
  • Please do not submit more than one feature or bug fix per pull request.
  • Implement your new feature or bug fix on your branch.
  • For consistency, and to enhance the chances that your contribution will be passed for review without corrections required, ensure that your code conforms to our current approach. For more information, see the BUILD Style Guide.
  • Be sure your author field in Git is filled out correctly, including full name and email address. This enables us to credit you for your contribution.
  1. Perform the requisite pre-pull request testing procedures. Please include tests to prove your code works.

A link to a comprehensive guide to testing new code prior to submitting your pull request will be inserted shortly.

  1. Push the changes on your fork, and submit pull request for original repository. Fore more information, see Using Pull Requests.

Note: For guidelines on commit messages, see the BUILD Style Guide.

  1. When you have submitted a pull request, a reviewer on the project team reviews your contribution to evaluate whether it can be committed to the master copy of the project, whether further discussion and development for further consideration, or whether it is not accepted as a contribution. It is generally expected that some communication is required with contributors after they have submitted a pull request, and quite rare that a contribution is accepted without qualification on the first attempt. To identify reviewers and committers for each module, click here.

###Links to Contribution-Related Documents

Clone this wiki locally