Skip to content

Latest commit

 

History

History
38 lines (29 loc) · 2.89 KB

CONTRIBUTING.md

File metadata and controls

38 lines (29 loc) · 2.89 KB
Raw

How to Contribute

We'd love to accept your contributions (currently only accepted from contributors within the SAS organisation) and updates to this project. There are just a few small guidelines you need to follow.

Contributor License Agreement

Contributions to this project must be accompanied by a signed Contributor Agreement. You (or your employer) retain the copyright to your contribution, this simply gives us permission to use and redistribute your contributions as part of the project.

Checklist before contributing

When adding your contribution using a Pull Request, confirm the following:

  1. Confirm that you have the right to submit the code that is being contributed. Please consider the origin of your code and confirm you have the appropriate rights to make the submission subject to the Apache 2.0 license that applies to everything in this repository of custom steps. If so, follow the instructions for the Contributor Agreement (which is based on the industry-standard Developer Certificate of Origin (DCO))
  2. Confirm that your contribution does not include any personally identifiable information (PII), for example, in any examples used in your README file.
  3. Confirm your contribution does not include any encryption or other export-controlled technology.
  4. Please adhere to the Data Guidance provided under the documentation section of this repository. It is important to use data only within the license conditions and permissibility provided by the source. Further, SAS may have additional requirements and guidelines regarding references to and usage of data.

Guidelines for contributions

  1. Contributions are accepted as a pull request made from a fork of this project. To elaborate, when you are ready to make a contribution,

    1. Create a fork of this project
    2. Create a branch (preffered) from the fork, naming it after your intended contribution (e.g. add-loan-demo)
    3. Using the provided _template folder as a guide, add your demo related assets to a folder in the branch.
    4. Create a pull request asking for a merge of your branch to the main branch of this project
    5. Maintainers will get in touch with you in case of any questions and required changes.

  2. Consider how an external user accesses your code for the first time, and make your demo assets as self-contained as possible.

  3. As a special consideration for any data required for the demo, please refer the Data Guidance for instructions.

  4. Recommendations on SAS programming best practices can be found here.

  5. All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose. Consult GitHub Help for more information on using pull requests in general.