Skip to content

Commit a70c859

Browse files
committed
Update contributing docs
- Move the contributing docs to the `docs/` directory - Convert the Code of Conduct to reStructuredText - Convert Contributing to reStructuredText and update the document - Add the contributing docs to the on-line documentation
1 parent 5b40da0 commit a70c859

File tree

4 files changed

+152
-48
lines changed

4 files changed

+152
-48
lines changed

CONTRIBUTING.md

Lines changed: 0 additions & 19 deletions
This file was deleted.
Lines changed: 20 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,16 @@
1-
# Contributor Covenant Code of Conduct
1+
.. _CodeOfConduct:
22

3-
## Our Pledge
3+
====================================
4+
Contributor Covenant Code of Conduct
5+
====================================
6+
7+
Our Pledge
8+
==========
49

510
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
611

7-
## Our Standards
12+
Our Standards
13+
=============
814

915
Examples of behavior that contributes to creating a positive environment include:
1016

@@ -22,25 +28,29 @@ Examples of unacceptable behavior by participants include:
2228
* Publishing others' private information, such as a physical or electronic address, without explicit permission
2329
* Other conduct which could reasonably be considered inappropriate in a professional setting
2430

25-
## Our Responsibilities
31+
Our Responsibilities
32+
====================
2633

2734
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
2835

2936
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
3037

31-
## Scope
38+
Scope
39+
=====
3240

3341
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
3442

35-
## Enforcement
43+
Enforcement
44+
===========
3645

3746
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
3847

3948
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
4049

41-
## Attribution
50+
Attribution
51+
===========
4252

43-
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
53+
This Code of Conduct is adapted from the `Contributor Covenant`_, `version 1.4`_.
4454

45-
[homepage]: http://contributor-covenant.org
46-
[version]: http://contributor-covenant.org/version/1/4/
55+
.. _Contributor Covenant: http://contributor-covenant.org
56+
.. _version 1.4: http://contributor-covenant.org/version/1/4/

docs/contributing.rst

Lines changed: 115 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,115 @@
1+
.. _Contributing:
2+
3+
============
4+
Contributing
5+
============
6+
7+
*webexteamssdk* is a community development project. Feedback, thoughts, ideas, and code contributions are most welcome!
8+
9+
10+
How to contribute Feedback, Issues, Thoughts and Ideas
11+
=======================================================
12+
13+
Please use the `issues`_ page to report issues or post ideas for enhancement.
14+
15+
Join our `webexteamssdk - Webex Teams SDK - Python Community Contributors <https://eurl.io/#BJ0A8gfOQ>`_ Webex Teams space to join the conversation with other contributors to this project.
16+
17+
18+
19+
Interested in Contributing Code?
20+
================================
21+
22+
23+
Developer Scripts
24+
-----------------
25+
26+
We have created some scripts to automate everyday actions needed when working on the project. Please see the `script`_ directory, and it's README for more information.
27+
28+
29+
Notes on the Test Suite
30+
-----------------------
31+
32+
To test all the API endpoints, the account that you use for testing must be an *admin* user for your Webex Teams Organization. Additionally, you should know that that the testing process creates some test people, rooms, messages, teams, and etc. as part of executing the test suite. We strongly recommend *NOT* running the test suite using your personal Webex Teams account (not that you can't; it's just that you probably don't want it cluttering your account with all these test artifacts).
33+
34+
If you cannot create a test account with *admin* privileges or configure your environment to run the test suite locally, you may always submit your code via a pull request. Our GitHub/Travis CI setup runs the test suite against all pull requests. All tests must pass before your pull request is accepted.
35+
36+
37+
Contributing Code - Using the CI Automated Testing
38+
--------------------------------------------------
39+
40+
1. Check for open `issues`_ or create a new *issue* for the item you want to work on and make sure to comment and let us know that you are working on it.
41+
42+
2. Fork a copy of the `repository`_ and clone your forked repository to your development environment.
43+
44+
3. Run ``script/setup`` to install the development dependencies and setup your environment.
45+
46+
4. Configure the following environment variables in your development environment:
47+
48+
* ``WEBEX_TEAMS_ACCESS_TOKEN`` - Your test account's Webex Teams access token.
49+
50+
5. Add your code to your forked repository.
51+
52+
If you are creating some new feature or functionality (excellent!), please also write a `test`_ to verify that your code works as expected.
53+
54+
6. We follow `PEP8`_ reasonably strictly for this project. Please make sure your code passes the linter.
55+
56+
Run ``script/test lint`` or simply run ``flake8`` from the project root.
57+
58+
7. Commit your changes.
59+
60+
8. Submit a `pull request`_. The GitHub/Travis CI system runs the test suite against your pull request code. If any tests fail, please review your changes. If everything looks good, we will gladly merge your request!
61+
62+
63+
Contributing Code - Running the Test Suite Locally
64+
--------------------------------------------------
65+
66+
1. Check for open `issues`_ or create a new 'issue' for the item you want to work on and make sure to comment and let us know that you are working on it.
67+
68+
2. Fork a copy of the `repository`_ and clone your forked repository to your development environment.
69+
70+
Run ``script/setup`` to install the development dependencies and setup your environment.
71+
72+
3. Configure the following environment variables in your development environment:
73+
74+
* ``WEBEX_TEAMS_ACCESS_TOKEN`` - Your test account's Webex Teams access token.
75+
76+
* ``WEBEX_TEAMS_TEST_DOMAIN`` - The test suite creates some users as part of the testing process. The test suite uses this domain name as the e-mail suffix of for the user's e-mail addresses.
77+
78+
* ``WEBEX_TEAMS_TEST_ID_START`` - The test suite uses this integer as the starting number for creating test user accounts (example: "[email protected]").
79+
80+
* ``WEBEX_TEAMS_TEST_FILE_URL`` - Configure this environment variable with a URL referencing a file that can be downloaded and posted to Webex Teams as part of the testing process.
81+
82+
*Example:*
83+
84+
.. code-block:: bash
85+
86+
#!/usr/bin/env bash
87+
export WEBEX_TEAMS_ACCESS_TOKEN="<test account's access token>"
88+
export WEBEX_TEAMS_TEST_DOMAIN="domain.com"
89+
export WEBEX_TEAMS_TEST_ID_START=42
90+
export WEBEX_TEAMS_TEST_FILE_URL="https://www.webex.com/content/dam/wbx/us/images/dg-integ/teams_icon.png"
91+
92+
93+
4. Add your code to your forked repository.
94+
95+
If you are creating some new feature or functionality (excellent!), please also write a `test`_ to verify that your code works as expected.
96+
97+
5. We follow `PEP8`_ reasonably strictly for this project. Please make sure your code passes the linter.
98+
99+
Run ``script/test lint`` or simply run ``flake8`` from the project root.
100+
101+
6. Commit your changes.
102+
103+
7. Ensure your code passes all of the default tests.
104+
105+
Run ``script/test`` and ensure all tests execute successfully.
106+
107+
8. Submit a `pull request`_. If everything looks good, we will gladly merge your request!
108+
109+
110+
.. _script: https://github.com/CiscoDevNet/webexteamssdk/tree/master/script
111+
.. _issues: https://github.com/CiscoDevNet/webexteamssdk/issues
112+
.. _repository: https://github.com/CiscoDevNet/webexteamssdk
113+
.. _test: https://github.com/CiscoDevNet/webexteamssdk/tree/master/tests
114+
.. _PEP8: https://www.python.org/dev/peps/pep-0008/
115+
.. _pull request: https://github.com/CiscoDevNet/webexteamssdk/pulls

docs/index.rst

Lines changed: 17 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -8,22 +8,17 @@ webexteamssdk
88

99
-------------------------------------------------------------------------------
1010

11-
Welcome to the docs! webexteamssdk is a *community developed* Pythonic
12-
wrapping of the Webex Teams APIs. The package represents all of the Cisco
13-
Webex Teams API interactions via native Python tools. Making working with the Cisco
14-
Webex Teams APIs in Python a *native* and *natural* experience.
11+
Welcome to the docs! webexteamssdk is a *community developed* Pythonic wrapping of the Webex Teams APIs. The package represents all of the Cisco Webex Teams API interactions via native Python tools. Making working with the Cisco Webex Teams APIs in Python a *native* and *natural* experience.
1512

16-
**webexteamssdk helps you get things done faster.** We take
17-
care of the API semantics, and you can focus on writing your code.
13+
**webexteamssdk helps you get things done faster.** We take care of the API semantics, and you can focus on writing your code.
1814

1915
With webexteamssdk, you can easily:
2016

2117
* Interact with the Webex Teams APIs in an interactive Python session
2218

2319
* Quickly create code that enables you get something done in Webex Teams
2420

25-
* Leverage the API wrapper to cleanly add Webex Teams functionality to your project
26-
without having to write the boilerplate code for working with the Webex Teams APIs
21+
* Leverage the API wrapper to cleanly add Webex Teams functionality to your project without having to write the boilerplate code for working with the Webex Teams APIs
2722

2823
To *dive in* and see how webexteamssdk makes your life better, check out the
2924
:ref:`Quickstart`!
@@ -40,11 +35,17 @@ The User Guide
4035
user/api
4136

4237

43-
The Community Guide
44-
===================
38+
The Development Community
39+
=========================
40+
41+
Interested in contributing to the project? Please review our community's Code of Conduct and then check out the Contributing page for info to help you get started.
42+
43+
.. toctree::
44+
:maxdepth: 1
45+
46+
code_of_conduct
47+
contributing
4548

46-
Community developer docs are *coming soon*. For now, please see the
47-
contribution_ instructions on the webexteamssdk_ GitHub page to get started.
4849

4950

5051
General Information about the Webex Teams Service
@@ -53,18 +54,15 @@ General Information about the Webex Teams Service
5354
What is Webex Teams?
5455
--------------------
5556

56-
"Webex Teams is where all your work lives. Bring your teams together in a
57-
place that makes it easy to keep people and work connected."
57+
"Webex Teams is where all your work lives. Bring your teams together in a place that makes it easy to keep people and work connected."
58+
59+
Visit the official `Webex Teams`_ website for more information and to create a `free account`_!
5860

59-
Check out the official `Webex Teams`_ website for more information and to
60-
create a free account!
6161

6262
Webex Teams for Developers
6363
--------------------------
6464

65-
Leveraging the Webex Teams APIs and developing on top of the Webex Teams cloud
66-
is easy. Signup for a `free account`_ and then head over to the
67-
`Webex Teams for Developers`_ website to learn more.
65+
Leveraging the Webex Teams APIs and developing on top of the Webex Teams cloud is easy. Signup for a `free account`_ and then head over to the `Webex Teams for Developers`_ website to learn more.
6866

6967

7068
*Copyright (c) 2016-2018 Cisco and/or its affiliates.*

0 commit comments

Comments
 (0)