Merge pull request #24 from spacetelescope/v0.2-epic

Merging v0.2 epic branch

.gitignore

@@ -1,60 +1,124 @@
-# Compiled files
+# Byte-compiled / optimized / DLL files
+__pycache__/
 *.py[cod]
-*.a
-*.o
+*$py.class
+
+# C extensions
 *.so
-__pycache__
 
-# Ignore .c files by default to avoid including generated code. If you want to
-# add a non-generated .c extension, use `git add -f filename.c`.
-*.c
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+pip-wheel-metadata/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
 
-# Other generated files
-*/version.py
-*/cython_version.py
-htmlcov
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
 .coverage
-MANIFEST
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+.hypothesis/
+.pytest_cache/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+target/
+
+# Jupyter Notebook
 .ipynb_checkpoints
 
-# Sphinx
-docs/api
-docs/_build
+# IPython
+profile_default/
+ipython_config.py
 
-# Eclipse editor project files
-.project
-.pydevproject
-.settings
+# pyenv
+.python-version
 
-# Pycharm editor project files
-.idea
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
 
-# Floobits project files
-.floo
-.flooignore
+# celery beat schedule file
+celerybeat-schedule
 
-# Packages/installer info
-*.egg
-*.egg-info
-dist
-build
-eggs
-parts
-bin
-var
-sdist
-develop-eggs
-.installed.cfg
-distribute-*.tar.gz
+# SageMath parsed files
+*.sage.py
 
-# Other
-.cache
-.tox
-.*.sw[op]
-*~
-.project
-.pydevproject
-.settings
-
-# Mac OSX
-.DS_Store
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/

.travis.yml

@@ -1,127 +1,14 @@
-# We set the language to c because python isn't supported on the MacOS X nodes
-# on Travis. However, the language ends up being irrelevant anyway, since we
-# install Python ourselves using conda.
-language: c
-
-os:
-    - linux
-
-# Setting sudo to false opts in to Travis-CI container-based builds.
 sudo: false
-
-# The apt packages below are needed for sphinx builds. A full list of packages
-# that can be included can be found here:
-#
-# https://github.com/travis-ci/apt-package-whitelist/blob/master/ubuntu-precise
-
-addons:
-    apt:
-        packages:
-            - graphviz
-            - texlive-latex-extra
-            - dvipng
-
-env:
-    global:
-
-        # The following versions are the 'default' for tests, unless
-        # overridden underneath. They are defined here in order to save having
-        # to repeat them for all configurations.
-        - PYTHON_VERSION=3.6
-        - NUMPY_VERSION=stable
-        - ASTROPY_VERSION=stable
-        - MAIN_CMD='python setup.py'
-        - SETUP_CMD='test'
-        - PIP_DEPENDENCIES=''
-        - EVENT_TYPE='pull_request push'
-
-
-        # List other runtime dependencies for the package that are available as
-        # conda packages here.
-        - CONDA_DEPENDENCIES='astropy'
-
-        # List other runtime dependencies for the package that are available as
-        # pip packages here.
-        - PIP_DEPENDENCIES='pygithub jira'
-
-
-        # Conda packages for affiliated packages are hosted in channel
-        # "astropy" while builds for astropy LTS with recent numpy versions
-        # are in astropy-ci-extras. If your package uses either of these,
-        # add the channels to CONDA_CHANNELS along with any other channels
-        # you want to use.
-        - CONDA_CHANNELS='astropy-ci-extras astropy'
-
-        # If there are matplotlib or other GUI tests, uncomment the following
-        # line to use the X virtual framebuffer.
-        # - SETUP_XVFB=True
-
-    matrix:
-        # Make sure that egg_info works without dependencies
-        - PYTHON_VERSION=3.5 SETUP_CMD='egg_info'
-        - PYTHON_VERSION=3.6 SETUP_CMD='egg_info'
-
+dist: bionic
+language: python
+python: 3.7
 matrix:
-
-    # Don't wait for allowed failures
-    fast_finish: true
-
     include:
-        # Try MacOS X
-        - os: osx
-          env: SETUP_CMD='test'
-
-        # Do a coverage test.
-        - os: linux
-          env: SETUP_CMD='test --coverage'
-
-        # Check for sphinx doc build warnings - we do this first because it
-        # may run for a long time
-        - os: linux
-          env: SETUP_CMD='build_docs -w'
-
-        - os: linux
-          env: ASTROPY_VERSION=lts
-
-        # Do a PEP8 test with pycodestyle
-        - os: linux
-          env: MAIN_CMD='pycodestyle jirahub --count' SETUP_CMD=''
-
-    allow_failures:
-        # Do a PEP8 test with pycodestyle
-        # (allow to fail unless your code completely compliant)
-        - os: linux
-          env: MAIN_CMD='pycodestyle jirahub --count' SETUP_CMD=''
-
+        - env: TOXENV=py37
+        - env: TOXENV=black
+        - env: TOXENV=flake8
+        - env: TOXENV=docs
+        - env: TOXENV=coverage
 install:
-
-    # We now use the ci-helpers package to set up our testing environment.
-    # This is done by using Miniconda and then using conda and pip to install
-    # dependencies. Which dependencies are installed using conda and pip is
-    # determined by the CONDA_DEPENDENCIES and PIP_DEPENDENCIES variables,
-    # which should be space-delimited lists of package names. See the README
-    # in https://github.com/astropy/ci-helpers for information about the full
-    # list of environment variables that can be used to customize your
-    # environment. In some cases, ci-helpers may not offer enough flexibility
-    # in how to install a package, in which case you can have additional
-    # commands in the install: section below.
-
-    - git clone --depth 1 git://github.com/astropy/ci-helpers.git
-    - source ci-helpers/travis/setup_conda.sh
-
-    # As described above, using ci-helpers, you should be able to set up an
-    # environment with dependencies installed using conda and pip, but in some
-    # cases this may not provide enough flexibility in how to install a
-    # specific dependency (and it will not be able to install non-Python
-    # dependencies). Therefore, you can also include commands below (as
-    # well as at the start of the install section or in the before_install
-    # section if they are needed before setting up conda) to install any
-    # other dependencies.
-
-script:
-   - $MAIN_CMD $SETUP_CMD
-
-after_success:
-    # If coveralls.io is set up for this package, uncomment the line below.
-    # The coveragerc file may be customized as needed for your package.
-    # - if [[ $SETUP_CMD == *coverage* ]]; then coveralls --rcfile='jirahub/tests/coveragerc'; fi
+    - pip install tox
+script: tox

CHANGES.rst

@@ -0,0 +1,11 @@
+0.2.0 (unreleased)
+------------------
+
+- Introduce configuration file
+- Major breaking changes to IssueSync class
+- Remove GithubQuery and JiraQuery classes
+
+0.1.0 (2019-07-19)
+------------------
+
+- Initial release

CODE_OF_CONDUCT.md

@@ -1,6 +1,6 @@
 # Spacetelescope Open Source Code of Conduct
 
-We expect all "spacetelescope" organization projects to adopt a code of conduct that ensures a productive, respectful environment for all open source contributors and participants. We are committed to providing a strong and enforced code of conduct and expect everyone in our community to follow these guidelines when interacting with others in all forums. Our goal is to keep ours a positive, inclusive, successful, and growing community. The community of participants in open source Astronomy projects is made up of members from around the globe with a diverse set of skills, personalities, and experiences. It is through these differences that our community experiences success and continued growth. 
+We expect all "spacetelescope" organization projects to adopt a code of conduct that ensures a productive, respectful environment for all open source contributors and participants. We are committed to providing a strong and enforced code of conduct and expect everyone in our community to follow these guidelines when interacting with others in all forums. Our goal is to keep ours a positive, inclusive, successful, and growing community. The community of participants in open source Astronomy projects is made up of members from around the globe with a diverse set of skills, personalities, and experiences. It is through these differences that our community experiences success and continued growth.
 
 
 As members of the community,
@@ -21,4 +21,4 @@ This code of conduct applies to all community situations online and offline, inc
 
 Parts of this code of conduct have been adapted from the Astropy and Numfocus codes of conduct.
 http://www.astropy.org/code_of_conduct.html
-https://www.numfocus.org/about/code-of-conduct/
+https://www.numfocus.org/about/code-of-conduct/

CONTRIBUTING.md

@@ -0,0 +1,16 @@
+Please open a new issue or new pull request for bugs, feedback, or new features
+you would like to see. If there is an issue you would like to work on, please
+leave a comment and we will be happy to assist. New contributions and
+contributors are very welcome!
+
+The main development work is done on the "master" branch. The rest of the branches
+are for release maintenance and should not be used normally. Unless otherwise told by a
+maintainer, pull request should be made and submitted to the "master" branch.
+
+New to GitHub or open source projects? If you are unsure about where to start or
+haven't used GitHub before, please feel free to contact the package maintainers.
+
+Feedback and feature requests? Is there something missing you would like to see?
+Please open an issue or send an email to the maintainers. This package follows
+the Spacetelescope [Code of Conduct](CODE_OF_CONDUCT.md) and strives to provide
+a welcoming community to all of our users and contributors.