feat: init packages with lerna

Signed-off-by: Olivier Albertini <[email protected]>

.commitlintrc.yml

@@ -0,0 +1,27 @@
+extends:
+  - '@commitlint/config-conventional'
+rules:
+  header-max-length: [1, 'always', 72]
+  type-enum:
+  - 2
+  - always
+  - - ci
+    - feat
+    - fix
+    - docs
+    - style
+    - refactor
+    - perf
+    - test
+    - revert
+help: |
+  **Possible types**:
+  `ci`:       Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
+  `feat`:     Adds a new feature.
+  `fix`:      Solves a bug.
+  `docs`:     Adds or alters documentation. (example scopes: readme, worker, code_of_conduct, contributors)
+  `style`:    Improves formatting, white-space.
+  `refactor`: Rewrites code without feature, performance or bug changes.
+  `perf`:     Improves performance.
+  `test`:     Adds or modifies tests. (example scopes: functionals, unit-tests)
+  `revert`:   Changes that reverting other changes

.dockerignore

@@ -0,0 +1,4 @@
+node_modules
+docker
+coverage
+.*

.github/ISSUE_TEMPLATE/bug.md

@@ -0,0 +1,26 @@
+---
+name: 🐛 Bug report
+labels: ':bug: Bug'
+about: Create a report to help us improve
+---
+
+## 🐛 Bug Report
+
+A clear and concise description of what the bug is.
+
+## To Reproduce
+
+Steps to reproduce the behavior:
+
+## Expected behavior
+
+A clear and concise description of what you expected to happen.
+
+## Link to repl or repo (highly encouraged)
+
+Please provide either a [repl.it demo](https://repl.it) or a minimal repository on GitHub.
+
+## Your environment
+Nodejs: 
+workit-camunda:
+Windows/Mac

.github/ISSUE_TEMPLATE/feature.md

@@ -0,0 +1,21 @@
+---
+name: 🚀 Feature Proposal
+labels: ':rocket: Feature Request'
+about: Submit a proposal for a new feature
+---
+
+## 🚀 Feature Proposal
+
+A clear and concise description of what the feature is.
+
+## Motivation
+
+Please outline the motivation for the proposal.
+
+## Example
+
+Please provide an example for how this feature would be used.
+
+## Pitch
+
+Why does this feature belong in the library

.github/ISSUE_TEMPLATE/regression.md

@@ -0,0 +1,30 @@
+---
+name: 💥 Regression Report
+labels: ':boom: Regression'
+about: Report unexpected behavior that worked in previous versions
+---
+
+
+## 💥 Regression Report
+
+A clear and concise description of what the regression is.
+
+## Last working version
+
+Worked up to version:
+
+Stopped working in version:
+
+## To Reproduce
+
+Steps to reproduce the behavior:
+
+## Expected behavior
+
+A clear and concise description of what you expected to happen.
+
+## Link to repl or repo (highly encouraged)
+
+Please provide either a [repl.it demo](https://repl.it) or a minimal repository on GitHub.
+
+Issues without a reproduction link are likely to stall.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,7 @@
+
+- [ ] My pull request adheres to the following guidelines
+- [ ] Search previous suggestions before making a new one, as yours may be a duplicate.
+
+closes #
+
+Thanks for contributing!

.gitignore

@@ -0,0 +1,55 @@
+node_modules/
+lerna-debug.log
+packages/*/lib
+.idea
+# Add any directories, files, or patterns you don't want to be tracked by version control
+.vscode
+npm-debug.log
+typings
+.tags*
+
+# OSX
+.DS_Store
+**/.DS_Store
+
+**/swagger.json
+.nyc_output/
+
+### Node ###
+# Logs
+logs
+*.log
+log
+*.log.*
+npm-debug.log*
+
+# Runtime data
+pids
+*.pid
+*.seed
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+
+# Optional npm cache directory
+.npm
+
+# Optional REPL history
+.node_repl_history
+
+# Created by docker/run
+/.cache.tgz
+/docker/.cache.tgzs
+/Running
+
+# Artillery reports
+/bin/artillery*report.json
+
+#ignore transpile code
+dist
+
+local.json
+local.yaml

CODE_OF_CONDUCT.md

@@ -0,0 +1,4 @@
+
+# Code of Conduct
+
+Ville de Montreal has adopted a Code of Conduct that we expect project participants to adhere to. Please read the [full text](http://ville.montreal.qc.ca/pls/portal/docs/page/intra_fr/media/documents/code_conduite_employes.pdf) so that you can understand what actions will and will not be tolerated.

CONTRIBUTING.md

@@ -0,0 +1,44 @@
+# How to Contribute
+
+This library is one of the open source projects of the Ville de Montréal which is currently under active development and which is also used to operate online services on [beta.montreal.com](https://beta.montreal.com).
+
+## [Code of Conduct](http://ville.montreal.qc.ca/pls/portal/docs/page/intra_fr/media/documents/code_conduite_employes.pdf)
+
+Ville de Montreal has adopted a Code of Conduct that we expect project participants to adhere to. Please read [the full text](http://ville.montreal.qc.ca/pls/portal/docs/page/intra_fr/media/documents/code_conduite_employes.pdf) so that you can understand what actions will and will not be tolerated.
+
+## Open Development
+
+All work on this library happens directly on [GitHub](/). Both core team members and external contributors send pull requests which go through the same review process.
+
+### `master` is unsafe
+
+We will do our best to keep `master` in good shape, with tests passing at all times. But in order to move fast, we will make API changes that your application might not be compatible with. We will do our best to communicate these changes and always version appropriately so you can lock into a specific version if need be.
+
+### Github
+
+My PR addresses the following Github issues and references them in the PR title. For example, "#XXX My PR"
+In case you are fixing a typo in the documentation you can prepend your commit with #XXX, code changes always need a Github issue.
+
+#### Description
+  Here are some details about my PR, including screenshots of any UI changes:
+
+  - Clarify the documentation.
+  - No UI changes.
+
+#### Tests
+
+  My PR adds the following unit tests OR does not need testing for this extremely good reason:
+
+  - It's just a simple documentation change.
+
+#### Commits
+  My commits all reference Github issues in their subject lines (recommended), 
+  and I have **squashed** multiple commits if they address the same issue. 
+  In addition, my commits follow the guidelines from ["How to write a good git commit message"](https://www.conventionalcommits.org/en/v1.0.0-beta.3)
+
+#### Documentation
+  In case of new functionality, my PR adds documentation that describes how to use it.
+
+## Developer Certificate of Origin (DCO)
+In order to accept your pull request, we need you to submit a DCO. You only need to add `-s` command line option to append this automatically to your commit message.
+[More details](https://github.com/probot/dco)

CONTRIBUTORS.md

@@ -0,0 +1,4 @@
+# Contributors
+
+* **Yann Debonnel** - [Ville de Montréal](https://github.com/VilledeMontreal)
+* **Zakaria Chérif Chérid** - [Ville de Montréal](https://github.com/VilledeMontreal)