Merge branch 'DistrictDataLabs:develop' into develop

Author: kbelita

.appveyor.yml

@@ -0,0 +1,20 @@
+# Set the default behavior, in case contributors don't have core.autocrlf set.
+* text=auto
+
+# Explicitly declare text files
+*.py text
+*.rst text
+*.md text
+*.json text
+*.ipynb text
+*.cfg text
+
+# Baseline images are binary and should not be modified
+*.png binary
+*.jpg binary
+*.pdf binary
+
+# Compressed files are binary and should not be modified
+*.gz binary
+*.npz binary
+*.zip binary

.gitattributes

@@ -0,0 +1,8 @@
+# These are supported funding model platforms
+
+github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+custom: https://numfocus.org/donate

.github/FUNDING.yml

@@ -0,0 +1,36 @@
+---
+name: Bug report
+about: Create a report to help us improve
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+
+```python
+# Steps to reproduce the behavior (code snippet):
+# Should include imports, dataset loading, and execution
+# Add the traceback below
+```
+
+**Dataset**
+Did you use a specific dataset to produce the bug? Where can we access it?
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Traceback**
+
+```
+If applicable, add the traceback from the exception.
+```
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. macOS]
+ - Python Version [e.g. 2.7, 3.6, miniconda]
+ - Yellowbrick Version [e.g. 0.7]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,14 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+
+---
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Examples**
+Attach an image with an example of the proposed visualization (e.g. from wikipedia or a wireframe example you've drawn). If there are any references we should include in the documentation, please also include them.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,15 @@
+---
+name: Generic Issue
+about: Alert us to an issue or task for this project
+
+---
+
+**Describe the issue**
+A clear and concise description of what the issue is.
+
+<!-- If you have a question, note that you can email us via our listserve:
+     https://groups.google.com/forum/#!forum/yellowbrick -->
+
+<!-- This line alerts the Yellowbrick maintainers, feel free to use this
+     @ address to alert us directly in follow up comments -->
+@DistrictDataLabs/team-oz-maintainers

.github/ISSUE_TEMPLATE/generic_issue.md

@@ -0,0 +1,73 @@
+<!--
+# Welcome Contributor!
+
+Thank you for contributing to Yellowbrick, please follow the instructions below to get
+your PR started off on the right foot.
+
+## First Steps
+
+1. Are you merging from a feature branch into develop?
+
+    _If not, please create a feature branch and change your PR to merge from that branch
+    into the Yellowbrick `develop` branch._
+
+2. Does your PR have a title?
+
+    _Please ensure your PR has a short, informative title, e.g. "Enhances ParallelCoordinates with new andrews_curve parameter" or "Corrects bug in WhiskerPlot that causes index error"_
+
+3. Summarize your PR (HINT: See CHECKLIST/TEMPLATE below!)
+-->
+
+This PR fixes #issue_number _(If you are fixing a bug)_ which reported a bug that caused a problem to occur when users...
+
+_(or if you are introducing a new feature)_ which requested a feature to allow the user to...
+
+I have made the following changes:
+
+1.
+2.
+3.
+
+### Sample Code and Plot
+
+_If you are adding or modifying a visualizer, PLEASE include a sample plot here along with the code you used to generate it._
+
+### TODOs and questions
+
+<!--
+If this is a work-in-progress (WIP), list the changes you still need to make and/or questions or the Yellowbrick team. You can also mention extensions to your work that might be added as an issue to work on after the PR.
+-->
+
+Still to do:
+
+- [ ]
+- [ ]
+- [ ]
+
+Questions for the @DistrictDataLabs/team-oz-maintainers:
+
+- [ ]
+- [ ]
+
+### CHECKLIST
+
+<!--
+Here's a handy checklist to go through before submitting a PR, note that you can check a checkbox in Markdown by changing `- [ ]` to `- [x]` or you can create the PR and check the box manually.
+-->
+
+- [ ] _Is the commit message formatted correctly?_
+- [ ] _Have you noted the new functionality/bugfix in the release notes of the next release?_
+
+<!-- If you've changed any code -->
+
+- [ ] _Included a sample plot to visually illustrate your changes?_
+- [ ] _Do all of your functions and methods have docstrings?_
+- [ ] _Have you added/updated unit tests where appropriate?_
+- [ ] _Have you updated the baseline images if necessary?_
+- [ ] _Have you run the unit tests using `pytest`?_
+- [ ] _Is your code style correct (are you using PEP8, pyflakes)?_
+- [ ] _Have you documented your new feature/functionality in the docs?_
+
+<!-- If you've added to the docs -->
+
+- [ ] _Have you built the docs using `make html` (must be run from `docs/`)?_

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,14 @@
+**Deployed:** DayOfWeek, Month D, YYYY
+**Current Contributors:** [insert GitHub @username comma list]
+
+[Release description (1-2 paras)]
+
+**Major Changes:**
+
+- [Change 1]
+- [Change 2]
+
+Minor Changes:
+
+- [Change 1]
+- [Change 2]