You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
_Put an `x` in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request._
8
+
9
+
-[ ] I have read the [CONTRIBUTING](https://github.com/aws/sagemaker-python-sdk/blob/master/CONTRIBUTING.md) doc
10
+
-[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
11
+
-[ ] I have updated the [changelog](https://github.com/aws/sagemaker-python-sdk/blob/master/CHANGELOG.rst) with a description of my changes (if appropriate)
12
+
-[ ] I have updated any necessary [documentation](https://github.com/aws/sagemaker-python-sdk/blob/master/README.rst) (if appropriate)
13
+
14
+
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional
4
+
documentation, we greatly value feedback and contributions from our community.
5
+
6
+
Please read through this document before submitting any issues or pull requests to ensure we have all the necessary
7
+
information to effectively respond to your bug report or contribution.
8
+
9
+
10
+
## Reporting Bugs/Feature Requests
11
+
12
+
We welcome you to use the GitHub issue tracker to report bugs or suggest features.
13
+
14
+
When filing an issue, please check [existing open](https://github.com/aws/sagemaker-python-sdk/issues), or [recently closed](https://github.com/aws/sagemaker-python-sdk/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20), issues to make sure somebody else hasn't already
15
+
reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
16
+
17
+
* A reproducible test case or series of steps
18
+
* The version of our code being used
19
+
* Any modifications you've made relevant to the bug
20
+
* A description of your environment or deployment
21
+
22
+
23
+
## Contributing via Pull Requests
24
+
Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
25
+
26
+
1. You are working against the latest source on the *master* branch.
27
+
2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
28
+
3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
29
+
30
+
To send us a pull request, please:
31
+
32
+
1. Fork the repository.
33
+
2. Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
34
+
3. Include unit tests when you contribute new features or make bug fixes, as they help to a) prove that your code works correctly, and b) guard against future breaking changes to lower the maintenance cost.
35
+
4. Ensure local tests pass.
36
+
5. Update the [changelog](https://github.com/aws/sagemaker-python-sdk/blob/master/CHANGELOG.rst) with a description of your changes for any code contribution.
37
+
6. Commit to your fork using [clear and imperative commit messages](https://chris.beams.io/posts/git-commit/).
38
+
7. Send us a pull request, answering any default questions in the pull request interface.
39
+
8. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
40
+
41
+
GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
42
+
[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
43
+
44
+
45
+
## Finding contributions to work on
46
+
Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels ((enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any ['help wanted'](https://github.com/aws/sagemaker-python-sdk/labels/help%20wanted) issues is a great place to start.
47
+
48
+
49
+
## Code of Conduct
50
+
This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
51
+
For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
57
+
58
+
59
+
## Licensing
60
+
61
+
See the [LICENSE](https://github.com/aws/sagemaker-python-sdk/blob/master/LICENSE) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
62
+
63
+
We may ask you to sign a [Contributor License Agreement (CLA)](http://en.wikipedia.org/wiki/Contributor_License_Agreement) for larger changes.
@@ -56,7 +56,8 @@ SageMaker Python SDK is tested on: \* Python 2.7 \* Python 3.5
56
56
57
57
Licensing
58
58
~~~~~~~~~
59
-
SageMaker Python SDK is licensed under the Apache 2.0 License. It is copyright 2017 Amazon.com, Inc. or its affiliates. All Rights Reserved. The license is available at: http://aws.amazon.com/apache2.0/
59
+
SageMaker Python SDK is licensed under the Apache 2.0 License. It is copyright 2018 Amazon.com, Inc. or its affiliates. All Rights Reserved. The license is available at:
0 commit comments