|
1 | 1 | # How to Contribute
|
2 |
| -We'd love to accept your patches and contributions to this project. |
3 |
| -We just ask that you follow our contribution guidelines when you do. |
| 2 | +This project is community-driven, and we'd love to accept your patches and contributions. |
| 3 | +We just ask that you follow our contribution guidelines when you do. Refer |
| 4 | +to the [Contributor Handbook](https://sassoftware.github.io/contributor-handbook.html) |
| 5 | +for guidance. |
4 | 6 |
|
5 | 7 | ## Contributor License Agreement
|
6 | 8 | Contributions to this project must be accompanied by a signed [Contributor Agreement](ContributorAgreement.txt).
|
7 |
| -You (or your employer) retain the copyright to your contribution; this simply grants us permission to use and redistribute your contributions as part of the project. |
| 9 | +You (or your employer) retain the copyright to your contribution; this agreement simply grants |
| 10 | +us permission to use and redistribute your contributions as part of the project. |
8 | 11 |
|
9 |
| -## Code reviews |
10 |
| -All submissions to this project—including submissions from project members—require review. |
11 |
| -Our review process typically involves performing unit tests, development tests, integration tests, and security scans using internal SAS infrastructure. |
12 |
| -For this reason, we don’t often merge pull requests directly from GitHub. |
| 12 | +## Code Reviews |
| 13 | +All submissions to this project—including submissions from project members—require |
| 14 | +review. Our review process typically involves performing unit tests, development |
| 15 | +tests, integration tests, and security scans. |
13 | 16 |
|
14 |
| -Instead, we work with submissions internally first, vetting them to ensure they meet our security and quality standards. |
15 |
| -We’ll 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. |
| 17 | +## Pull Request Requirement |
| 18 | +All contributions (PRs) must be accompanied by passing unit and/or integration |
| 19 | +tests, following our [testing philosophy](./docs/user/TestingPhilosophy.md). If you are unfamiliar with this process, |
| 20 | +we are happy to help you navigate it by providing continuous collaboration within the pull request. |
| 21 | +All pull requests must also pass our linter analysis checks. Contributions might |
| 22 | +be subjected to security scans before they can be accepted. |
16 | 23 |
|
17 |
| -This does not mean we don’t value or appreciate your contribution. |
18 |
| -We simply need to review your code internally before merging it. |
19 |
| -We work to ensure all contributors receive appropriate recognition for their contributions, at least by acknowledging them in our release notes. |
| 24 | +## Security Scans |
| 25 | +To ensure that all submissions meet our security and quality standards, we perform security |
| 26 | +scans using internal SAS infrastructure. Reporting of any Common Vulnerabilities and Exposures |
| 27 | +(CVEs) that are detected is not available in this project at this time. |
0 commit comments