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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
-
#Contributing to the Optimizely Python SDK
1
+
#Contributing to the Optimizely Python SDK
2
2
We welcome contributions and feedback! All contributors must sign our [Contributor License Agreement (CLA)](https://docs.google.com/a/optimizely.com/forms/d/e/1FAIpQLSf9cbouWptIpMgukAKZZOIAhafvjFCV8hS00XJLWQnWDFtwtA/viewform) to be eligible to contribute. Please read the [README](README.md) to set up your development environment, then read the guidelines below for information on submitting your code.
3
3
4
-
##Development process
4
+
##Development process
5
5
6
6
1. Create a branch off of `devel`: `git checkout -b YOUR_NAME/branch_name`.
7
7
2. Commit your changes. Make sure to add tests!
@@ -11,22 +11,22 @@ We welcome contributions and feedback! All contributors must sign our [Contribut
11
11
6. Open a pull request from `YOUR_NAME/branch_name` to `devel`.
12
12
7. A repository maintainer will review your pull request and, if all goes well, merge it!
13
13
14
-
##Pull request acceptance criteria
14
+
##Pull request acceptance criteria
15
15
16
16
***All code must have test coverage.** We use unittest. Changes in functionality should have accompanying unit tests. Bug fixes should have accompanying regression tests.
17
17
* Tests are located in `/tests` with one file per class.
18
18
* Please don't change the `__version__`. We'll take care of bumping the version when we next release.
19
19
* Lint your code with PEP-8 before submitting.
20
20
21
-
##Style
21
+
##Style
22
22
We enforce PEP-8 rules with a few minor deviations.
23
23
24
-
##License
24
+
##License
25
25
26
26
All contributions are under the CLA mentioned above. For this project, Optimizely uses the Apache 2.0 license, and so asks that by contributing your code, you agree to license your contribution under the terms of the [Apache License v2.0](http://www.apache.org/licenses/LICENSE-2.0). Your contributions should also include the following header:
27
27
28
28
```
29
-
# Copyright 2016, Optimizely
29
+
# Copyright 2017, Optimizely
30
30
# Licensed under the Apache License, Version 2.0 (the "License");
31
31
# you may not use this file except in compliance with the License.
32
32
# You may obtain a copy of the License at
@@ -42,5 +42,5 @@ All contributions are under the CLA mentioned above. For this project, Optimizel
42
42
43
43
The YEAR above should be the year of the contribution. If work on the file has been done over multiple years, list each year in the section above. Example: Optimizely writes the file and releases it in 2014. No changes are made in 2015. Change made in 2016. YEAR should be “2014, 2016”.
44
44
45
-
##Contact
45
+
##Contact
46
46
If you have questions, please contact developers@optimizely.com.
This repository houses the Python SDK for Optimizely Full Stack.
7
7
8
-
##Getting Started
8
+
##Getting Started
9
9
10
-
###Installing the SDK
10
+
###Installing the SDK
11
11
12
12
The SDK is available through [PyPi](https://pypi.python.org/pypi?name=optimizely-sdk&:action=display). To install:
13
13
14
14
```
15
15
pip install optimizely-sdk
16
16
```
17
17
18
-
###Using the SDK
18
+
###Using the SDK
19
19
See the Optimizely Full Stack [developer documentation](http://developers.optimizely.com/server/reference/index.html) to learn how to set up your first Python project and use the SDK.
20
20
21
-
##Development
21
+
##Development
22
22
23
-
###Building the SDK
23
+
###Building the SDK
24
24
25
25
Build the SDK using the following command:
26
26
@@ -36,16 +36,16 @@ You can then install the SDK and its dependencies with:
36
36
pip install dist/optimizely-sdk-{VERSION}.tar.gz
37
37
```
38
38
39
-
###Unit tests
39
+
###Unit tests
40
40
41
-
#####Running all tests
41
+
#####Running all tests
42
42
You can run all unit tests with:
43
43
44
44
```
45
45
nosetests
46
46
```
47
47
48
-
#####Running all tests in a file
48
+
#####Running all tests in a file
49
49
To run all tests under a particular test file you can use the following command:
50
50
51
51
```
@@ -58,7 +58,7 @@ For example, to run all tests under `test_event`, the command would be:
58
58
nosetests tests.test_event
59
59
```
60
60
61
-
#####Running all tests under a class
61
+
#####Running all tests under a class
62
62
To run all tests under a particular class of tests you can use the following command:
63
63
64
64
```
@@ -70,7 +70,7 @@ For example, to run all tests under `test_event.EventTest`, the command would be
70
70
nosetests tests.test_event:EventTest
71
71
```
72
72
73
-
#####Running a single test
73
+
#####Running a single test
74
74
To run a single test you can use the following command:
75
75
76
76
```
@@ -83,6 +83,6 @@ For example, to run `test_event.EventTest.test_dispatch`, the command would be:
0 commit comments