updated new content for developer docs

Author: corneliusyaovi

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,39 +1,54 @@
-<!--- Provide a general summary of your changes in the Title above -->
-
-#### Description
-<!--- Describe your changes in detail -->
-
-#### Related Issue
-<!--- This project only accepts pull requests related to open issues -->
-<!--- If suggesting a new feature or change, please discuss it in an issue first -->
-<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
-<!--- Please link to the issue here: -->
-
-#### Motivation and Context
-<!--- Why is this change required? What problem does it solve? -->
-
-#### How Has This Been Tested?
-<!--- Please describe in detail how you tested your changes. -->
-<!--- Include details of your testing environment, and the tests you ran to -->
-<!--- see how your change affects other areas of the code, etc. -->
-
-#### Types of changes
-<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
-- [ ] Bug fix (non-breaking change which fixes an issue)
-- [ ] Refactor (non-breaking change which improves implementation)
-- [ ] Performance (non-breaking change which improves performance. Please add associated performance test and results)
-- [ ] New feature (non-breaking change which adds functionality)
-- [ ] Breaking change (fix or feature that would cause existing functionality to change)
-- [ ] Non-functional change (xml comments/documentation/etc)
-
-#### Checklist:
-<!--- The following is a checklist of items that MUST be completed before a PR is accepted -->
-<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
-- [ ] My code follows the code style of this project.
-- [ ] I have read the **CONTRIBUTING** [document](https://github.com/QuantConnect/Lean/blob/master/CONTRIBUTING.md).
-- [ ] I have added tests to cover my changes. <!--- If not applicable, please explain why -->
-- [ ] All new and existing tests passed.
-- [ ] My branch follows the naming convention `bug-<issue#>-<description>` or `feature-<issue#>-<description>`
-
-
-@Flutterwave/Corvus97 What do you think about these updates?
+### Requirements for contributing to the library
+
+* Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
+* Include the issue link for bug fixes.
+* The pull request must include a test suite to demonstrate the changed functionality.
+* After you create the pull request, all status checks must pass before a maintainer reviews your contribution.
+
+### Type of change
+[] Bug fix
+[] Performance improvement
+[] Documentation update
+
+### Description of the change
+
+<!--
+
+We should understand the purpose of your change from this description. We would not review PRs with inadequate descriptions.
+
+-->
+
+
+### Related issue
+
+<!--
+
+Link to the issue that your change relates to. For feature requests, send us an email at developers@flutterwavego.com
+
+-->
+
+
+### Checklist
+
+[] I have read the contribution document.
+[] I have added tests to cover my changes.
+[] All new and existing tests passed.
+
+
+### Release Notes
+
+<!--
+
+Please describe the changes in a single line that explains this improvement in
+a user-friendly manner.  This text will be used in our release notes.
+
+If said change is not user-facing or notable enough to be included in release notes
+you may use "N/A" here.
+
+Examples:
+
+- The GitHub package now allows you to charge XAF payments.
+- Fixed an issue where payment plan creation returns an error.
+- Increased the performance of searching paginated responses.
+
+-->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -21,4 +21,5 @@ franc_test.py
 build/
 dist/
 rave_python.egg-info/
+staging
 

.github/ISSUE_TEMPLATE/other_issues.md

@@ -0,0 +1,91 @@
+Thank you for taking the time to contribute to our library🙌🏾.
+
+In this section, we detail everything you need to know about contributing to this library.
+
+
+**[Code of Conduct](https://github.com/probot/template/blob/master/CODE_OF_CONDUCT.md)**
+
+## **I don't want to contribute, I have a question**
+
+Please don't raise an issue to ask a question. You can ask questions on our [forum](http://forum.flutterwave.com) or developer [slack](https://bit.ly/34Vkzcg). We have an army of Engineers on hand to answer your questions there.
+
+## How can I contribute?
+
+### Reporting a bug
+
+Have you spotted a bug? Fantastic! Before raising an issue, here are some things to do:
+
+1. Search to see if another user has reported the bug. For existing issues that are still open, add a comment instead of creating a new one.
+2. Check our forum and developer slack to confirm that we did not address it there.
+
+When you report an issue, it is important to:
+
+1. Explain the problem
+    - Use a clear and descriptive title to help us to identify the problem.
+    - Describe steps we can use to replicate the bug and be as precise as possible.
+    - Include screenshots of the error messages.
+2. Include details about your configuration and setup
+    - What version of the library are you using?
+    - Did you experience the bug on test mode or live?
+    - Do you have the recommended versions of the library dependencies?
+
+<aside>
+
+💡 Please make use of the issue template when reporting bugs.
+
+</aside>
+
+### Requesting a feature
+
+If you need an additional feature added to the library, kindly send us an email at developers@flutterwavego.com. Be sure to include the following in your request:
+
+1. A clear title that helps us to identify the requested feature.
+2. A brief description of the use case for that feature.
+3. Explain how this feature would be helpful to your integration.
+4. Library name and version.
+
+### Submitting changes (PR)
+
+Generally, you can make any of the following changes to the library:
+
+1. Bug fixes
+2. Performance improvement
+3. Documentation update
+4. Functionality change (usually new features)
+
+<aside>
+
+💡 Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of the library will generally not be accepted.
+
+</aside>
+
+Follow these steps when making a pull request to the library:
+
+1. Fork the repository and create your branch from master.
+2. For all types of changes (excluding documentation updates), add tests for the changes.
+3. If you are making a functionality change, update the docs to show how to use the new feature.
+4. Ensure all your tests pass.
+5. Make sure your code lints.
+6. Write clear log messages for your commits. one-liners are fine for small changes, but bigger changes should have a more descriptive commit message (see sample below). 
+7. Use present tense for commit messages, "Add feature" not "Added feature”.
+8. Ensure that you fill out all sections of the PR template.
+9. Raise the PR against the `staging` branch.
+10. After you submit the PR, verify that all [status checks](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) are passing
+
+```markdown
+$ git commit -m "A brief summary of the commit
+> 
+> A paragraph describing what changed and its impact."
+```
+
+<aside>
+
+💡 For your pull request to be reviewed, you need to meet the requirements above. We may ask you to complete additional tests, or other changes before your pull request can be ultimately accepted.
+
+</aside>
+
+We encourage you to contribute and help make the library better for the community. Got questions? send us a [message](https://bit.ly/34Vkzcg).
+
+Thank you.
+
+The Flutterwave team 🦋

.github/PULL_REQUEST_TEMPLATE.md

@@ -10,49 +10,56 @@
 
 
 ## Introduction
-This is a Python wrapper around the [API](https://flutterwavedevelopers.readme.io/v2.0/reference) for [Rave by Flutterwave](https://rave.flutterwave.com).
-
-#### Payment types implemented:
-* Card Payments
-* Bank Account Payments
-* Ghana Mobile Money Payments
-* Mpesa Payments
-* Rwanda Mobile Money Payments
-* Uganda Mobile Money Payments
-* Zambia Mobile Money Payments
-* Mobile Money Payments for Francophone countries
-* Subaccounts
-* Transfer
-* Subscription (Recurring Payments)
-* Bills payment
-* Payment Plan
-* USSD Payments (Still in Beta Mode)
-
-#### Other features include:
-* Preauthorization charges
-* Refunds
-* Transaction Verification
-* Transfer Recipients
-* Virtual Cards
-* Virtual Accounts
+The Python library provides easy access to Flutterwave for Business (F4B) v2 APIs from Django, Flask, and other Python apps. It abstracts the complexity involved in direct integration and allows you to make quick calls to the APIs.
+
+Available features include:
+
+- Collections: Card, Account, Mobile money, Bank Transfers, USSD, Barter, NQR.
+- Payouts and Beneficiaries.
+- Recurring payments: Tokenization and Subscriptions.
+- Split payments
+- Card issuing
+- Transactions dispute management: Refunds.
+- Transaction reporting: Collections, Payouts, Settlements, and Refunds.
+- Bill payments: Airtime, Data bundle, Cable, Power, Toll, E-bills, and Remitta.
+- Identity verification: Resolve bank account, resolve BVN information.
+
+## Table of Contents
+1. [Requirements](#requirements)
+2. [Installation](#installation)
+3. [Initialization](#initialization)
+4. [Usage](#usage)
+5. [Testing](#testing)
+6. [Debugging Errors](#debugging-errors)
+7. [Support](#support)
+8. [Contribution guidelines](#)
+9. [License](#)
+10. [Changelog](#)
+
+## Requirements
+1. Flutterwave for business [API Keys](https://developer.flutterwave.com/docs/integration-guides/authentication)
+2. Acceptable Python versions: >=2.7, !=3.0.\*, !=3.1.\*, !=3.2.\*, !=3.3.\*, !=3.4.\*
+
 
 ## Installation
-To install, run
+To install the library, run
 
 ```sh
 pip install rave_python
 ```
 
 Note: This is currently under active development
-## Import Package
+
+
+## Initialization
+
+### Import Package
 The base class for this package is 'Rave'. To use this class, add:
 
 ```py
 from rave_python import Rave
 ```
 
-## Initialization
-
 #### To instantiate in sandbox:
 To use Rave, instantiate the Rave class with your public key. We recommend that you store your secret key in an environment variable named, ```RAVE_SECRET_KEY```. Instantiating your rave object is therefore as simple as:
 
@@ -75,7 +82,9 @@ To initialize in production, simply set the ```production``` flag to ```True```.
 rave = Rave("YOUR_PUBLIC_KEY", production=True)
 ```
 
-# Rave Objects
+
+
+# Usage
 This is the documentation for all of the components of rave_python
 
 ## ```rave.Card```
@@ -2775,7 +2784,8 @@ This call returns a dictionary. A sample response is:
 ```
 <br>
 
-## Run Tests
+
+## Testing
 
 All of the SDK's tests are written with Python's ```unittest``` module. The tests currently test:
 ```rave.Account```
@@ -2797,5 +2807,26 @@ python test.py
 >**NOTE:** The test may fail for account validation - ``` Pending OTP validation``` depending on whether the service is down or not
 <br>
 
+
+## Debugging Errors
+We understand that you may run into some errors while integrating our library. You can read more about our error messages [here](https://developer.flutterwave.com/docs/integration-guides/errors).
+
+For `authorization` and `validation` error responses, double-check your API keys and request. If you get a `server` error, kindly engage the team for support.
+
+
+
 ## Support
-For further assistance in using the SDK, you can contact the Developers on [Slack](https://join.slack.com/t/flutterwavedevelopers/shared_invite/enQtNTk3MjgxMjU3ODI5LWFkMjBkYTc0ZGJhM2Q5MTY3YjFkYzAyYmM1ZDZjZjUwMjE4YTc2NjQ1ZGM5ZWE4NDUxMzc4MmExYmI1Yjg5ZWU) and [Email](mailto:developers@flutterwavego.com). You can get more information about the amazing features here [here](https://developer.flutterwave.com/reference#introduction).
+For additional assistance using this library, contact the developer experience (DX) team via [email](mailto:developers@flutterwavego.com) or on [slack](https://bit.ly/34Vkzcg). 
+
+You can also follow us [@FlutterwaveEng](https://twitter.com/FlutterwaveEng) and let us know what you think 😊.
+
+
+## Contribution guidelines
+Read more about our community contribution guidelines [here](/CONTRIBUTING.md)
+
+
+## License
+
+By contributing to this library, you agree that your contributions will be licensed under its [MIT license](/LICENSE).
+
+Copyright (c) Flutterwave Inc.

.gitignore

@@ -5,10 +5,10 @@
 
 setuptools.setup(
     name="rave_python",
-    version="1.2.15",
+    version="1.2.16",
     author="Flutterwave",
     author_email="developers@flutterwavego.com",
-    description="Official Rave Python Wrapper By Flutterwave",
+    description="Python library for Flutterwave for Business (F4B) v2 APIs.",
     long_description=long_description,
     long_description_content_type="text/markdown",
     url="https://github.com/Flutterwave/rave-python",