Welcome, contributors
SAS is the founder and future of analytics.
When you contribute to SAS's open source projects, you'll build tools that help people make better decisions, faster.
Contributing to open source projects from SAS Institute Inc.
SAS is the founder and future of analytics.
When you contribute to SAS's open source projects, you'll build tools that help people make better decisions, faster.
SAS Software on GitHub is home to more than 200 open source projects from SAS. Find open projects, plugins, examples, and other resources for extending and integrating SAS's powerful tools with open source languages and frameworks.
Browse projects
If a SAS open source project is accepting contributions, the project repository will contain a CONTRIBUTING.md file. Read that file carefully. It will contain important instructions for contributing to the project. It might also offer details about the project's development and code review processes.
When you understand (and follow) these guidelines, you'll increase the likelihood that project maintainers will accept your contributions.
Everyone contributing to SAS projects must sign SAS's standard contributor agreement, which is built on the Developer Certificate of Origin.
To comply with the agreement and attest to your right to offer your contribution to a SAS project, simply add the following line to your commits:
Signed-off-by: Firstname Lastname <user@mail.com>For example:
Signed-off-by: Random J Developer <random@developer.example.org>You can add this line to your commits with this command:
git commit -sSAS uses the DCO app to scan all commits in incoming pull requests and confirm this sign-off. The app will alert you if your commits aren't properly signed-off. It will also offer instructions for remediating the issue and providing proper sign-off. SAS project maintainers won't merge your commit unless you've added proper sign-off.
Version 1.1
Contributions to this software are accepted only when they are properly accompanied by a Contributor Agreement. The Contributor Agreement for this software is the Developer's Certificate of Origin 1.1 (DCO) as provided with and required for accepting contributions to the Linux kernel.
In each contribution proposed to be included in this software, the developer must include a "sign-off" that denotes consent to the terms of the Developer's Certificate of Origin. The sign-off is a line of text in the description that accompanies the change, certifying that you have the right to provide the contribution to be included. For changes provided in source code control (for example, via a Git pull request) the sign-off must be included in the commit message in source code control. For changes provided in email or issue tracking, the sign-off must be included in the email or the issue, and the sign-off will be incorporated into the permanent commit message if the contribution is accepted into the official source code.
Read the full agreement
Each of SAS's open source projects has its own team of maintainers at SAS. Each one therefore has its own set of code conventions and review process, too.
A project's CONTRIBUTING.md file will detail the project's code review processes. All contributions require review from SAS project maintainers. They may run unit tests, development tests, integrations tests, and security scans using internal SAS infrastructure. In this case, they may not merge a contribution directly from GitHub; instead, they'll work with submissions internally first, vetting them to ensure they meet SAS standards.
We’ll always do our best to work with contributors in public issues and pull requests; however, to ensure our code meets our internal compliance standards, we may need to incorporate your submission into a solution we push ourselves. And we work to ensure all contributors receive appropriate recognition for their contributions—at the very least, by acknowledging contributors in our release notes.
Browse the SAS Software organization on GitHub.