Add initial code

Author: codingjoe

.bandit

@@ -0,0 +1,2 @@
+[bandit]
+exclude: tests

.checks.yml

@@ -0,0 +1,3 @@
+- bandit
+- flake8
+- pydocstyle

.editorconfig

@@ -0,0 +1,30 @@
+# http://editorconfig.org
+
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.py]
+indent_style = space
+indent_size = 4
+
+[*.{rst,ini,cfg}]
+indent_style = space
+indent_size = 4
+
+[*.{yml,html,xml,xsl,json}]
+indent_style = space
+indent_size = 2
+
+[*.{css,less}]
+indent_style = space
+indent_size = 2
+
+[*.dot]
+indent_style = tab
+indent_size = 1
+insert_final_newline = false

.gitignore

@@ -0,0 +1,104 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+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
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+.hypothesis/
+.pytest_cache/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# pyenv
+.python-version
+
+# celery beat schedule file
+celerybeat-schedule
+
+# SageMath parsed files
+*.sage.py
+
+# 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/

.travis.yml

@@ -0,0 +1,41 @@
+language: python
+sudo: true
+dist: xenial
+services:
+- redis-server
+- rabbitmq
+cache: pip
+python:
+- "3.5"
+- "3.6"
+- "3.7"
+addons:
+  apt:
+    packages:
+    - python3-enchant
+    - graphviz
+env:
+  matrix:
+  - DJANGO=20
+  - DJANGO=21
+  - DJANGO=master
+  - TOXENV=docs
+matrix:
+  fast_finish: true
+  allow_failures:
+  - env: DJANGO=master
+  exclude:
+  - python: "3.6"
+    env: TOXENV=docs
+  - python: "3.7"
+    env: TOXENV=docs
+before_script:
+- |
+  if [[ -z $TOXENV ]]; then
+    export TOXENV=py$(echo $TRAVIS_PYTHON_VERSION | sed -e 's/\.//g')-dj$DJANGO
+  fi
+- echo $TOXENV
+install:
+- pip install -U codecov tox
+script: tox -e $TOXENV
+after_success: codecov

CONTRIBUTING.md

@@ -0,0 +1,37 @@
+# How to contribute
+
+## Design Goals
+
+### M.U.S.T
+
+This package follows a couple of MUST have design principles.
+
+##### Maintainable
+
+The package and it is features needs to be maintainable. It is more important
+upgrade to the latest Django or Python release than it is to add more
+features.
+
+##### User friendly
+
+The features, as well as the code, should be accessible to users and first time
+contributors. Documentation is key!
+
+##### Specific
+
+A good package solves only one problem and solves it well. We don't want people
+to add code to their runtime environment that they don't need.
+
+##### Tested
+
+All features need to be tested. A CI suite should be in place. Running and
+writing tests should be reasonably accessible for first time contributors.
+
+
+## Release
+
+We follow [semantic versioning](https://semver.org/). To release a new version
+simply [create a new GitHub release][create-release], specify the version and
+add the changelog into the release description.
+
+[create-release]: https://github.com/codingjoe/galahad/releases/new

LICENSE

@@ -0,0 +1,15 @@
+ISC License
+
+Copyright (c) 2018, Johannes Hoppe
+
+Permission to use, copy, modify, and/or distribute this software for any
+purpose with or without fee is hereby granted, provided that the above
+copyright notice and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

README.md

@@ -0,0 +1,70 @@
+# Galahad
+
+**The workflow automation framework for machines with heart.**
+
+Galahad is a free workflow automation framework designed to bring simplicity
+to complex workflows.
+
+
+## Design
+
+### Principles 
+
+#### Common sense is better than convention
+
+Galahad does not follow any academic modeling notation developed by a poor Phd
+student who actually never worked a day in their life. Businesses are already
+complex which is why Galahad is rather simple. There are only two types of
+tasks – human & machine – as well as edges to connect them. It's so simple a
+toddler (or your CEO) could design a workflow.
+
+#### Lean Automation (breaking the rules)
+
+Things don't always go according to plan especially when humans are involved.
+Even the best workflow can't cover all possible edge cases. Galahad
+embraces that fact. It allows uses to interrupt a process at any given point
+and modify it's current state. All while tracking all changes. This allows
+developers to automate the main cases and users handle manually exceptions.
+This allows you businesses to ship prototypes and MVPs of workflows.
+Improvements can be shipped in multiple iterations without disrupting the
+business.
+
+#### People
+
+Galahad is build with all users in mind. Managers should be able to develop
+better processes. Users should able to interact with the tasks every single
+day. And developers should be able to rapidly develop and test new features.
+
+## Core Components
+
+### Process
+
+The `Process` object holds the state of a workflow instances. It is represented
+by a Django Model. This way all process states are persisted in your database.
+
+Processes are also the vehicle for the other two components `Tasks` and
+`edges`.
+
+### Task
+
+A task defines the behavior or a process. It can be considered as a simple
+transaction that changes state of a process. There are two types of tasks,
+human and machine tasks.
+
+Human tasks are represented by Django `View`s. A user can change the processes
+state via a Django form or a JSON API. 
+
+Machine tasks are represented by simple methods on the `Process` class. They
+can change the state and perform any action you can think of. They can decide
+which task to execute next (exclusive gateway) but also start or wait for multiple
+other tasks (split/join gateways).
+
+Furthermore tasks can implement things like sending emails or fetching data
+from an 3rd party API. All tasks are executed asynchronously to avoid blocking
+IO and locked to prevent raise conditions.
+
+### Edges
+
+Edges are the glue that binds tasks together. They define the transitions
+between tasks. They are represented by a simple list of tuples. Edges have no
+behavior but define the structure of a workflow.

docs/commands.rst

@@ -0,0 +1,10 @@
+===================
+Management Commands
+===================
+
+.. automodule:: galahad.management.commands
+
+render_process_graph
+--------------------
+
+Render graphs for all processes as SVG files to the working directory.