Update the contributing doc

Travis tests will not succeed for Pull Requests sent submitted by users other than Chris since Travis hasn't been configured with their Webex Teams access tokens (good security practice).

We will make sure the tests pass before pushing a release.

Author: cmlccie

docs/contributing.rst

@@ -31,11 +31,11 @@ Notes on the Test Suite
 
 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).
 
-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.
+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.  We will test your code before merging and releasing the changes.
 
 
-Contributing Code - Using the CI Automated Testing
---------------------------------------------------
+Contributing Code
+-----------------
 
 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.
 
@@ -57,54 +57,33 @@ Contributing Code - Using the CI Automated Testing
 
 7. Commit your changes.
 
-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!
-
-
-Contributing Code - Running the Test Suite Locally
---------------------------------------------------
-
-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.
-
-2. Fork a copy of the `repository`_ and clone your forked repository to your development environment.
-
-   Run ``script/setup`` to install the development dependencies and setup your environment.
-
-3. Configure the following environment variables in your development environment:
+8. Submit a `pull request`_.
 
-   * ``WEBEX_TEAMS_ACCESS_TOKEN`` - Your test account's Webex Teams access token.
-
-   * ``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.
-
-   * ``WEBEX_TEAMS_TEST_ID_START`` - The test suite uses this integer as the starting number for creating test user accounts (example: "test42@domain.com").
-
-   * ``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.
 
-   *Example:*
+Running the Test Suite Locally
+------------------------------
 
-   .. code-block:: bash
+Configure the following environment variables in your development environment:
 
-       #!/usr/bin/env bash
-       export WEBEX_TEAMS_ACCESS_TOKEN="<test account's access token>"
-       export WEBEX_TEAMS_TEST_DOMAIN="domain.com"
-       export WEBEX_TEAMS_TEST_ID_START=42
-       export WEBEX_TEAMS_TEST_FILE_URL="https://www.webex.com/content/dam/wbx/us/images/dg-integ/teams_icon.png"
+* ``WEBEX_TEAMS_ACCESS_TOKEN`` - Your test account's Webex Teams access token.
 
+* ``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.
 
-4. Add your code to your forked repository.
+* ``WEBEX_TEAMS_TEST_ID_START`` - The test suite uses this integer as the starting number for creating test user accounts (example: "test42@domain.com").
 
-   If you are creating some new feature or functionality (excellent!), please also write a `test`_ to verify that your code works as expected.
-
-5. We follow `PEP8`_ reasonably strictly for this project.  Please make sure your code passes the linter.
-
-   Run ``script/test lint`` or simply run ``flake8`` from the project root.
+* ``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.
 
-6. Commit your changes.
+*Example:*
 
-7. Ensure your code passes all of the default tests.
+.. code-block:: bash
 
-   Run ``script/test`` and ensure all tests execute successfully.
+   #!/usr/bin/env bash
+   export WEBEX_TEAMS_ACCESS_TOKEN="<test account's access token>"
+   export WEBEX_TEAMS_TEST_DOMAIN="domain.com"
+   export WEBEX_TEAMS_TEST_ID_START=42
+   export WEBEX_TEAMS_TEST_FILE_URL="https://www.webex.com/content/dam/wbx/us/images/dg-integ/teams_icon.png"
 
-8. Submit a `pull request`_.  If everything looks good, we will gladly merge your request!
+Ensure your code passes all of the default tests.  Run ``script/test`` and ensure all tests execute successfully.
 
 
 .. _script: https://github.com/CiscoDevNet/webexteamssdk/tree/master/script