first commit

.gitattributes

@@ -0,0 +1,63 @@
+###############################################################################
+# Set default behavior to automatically normalize line endings.
+###############################################################################
+* text=auto
+
+###############################################################################
+# Set default behavior for command prompt diff.
+#
+# This is need for earlier builds of msysgit that does not have it on by
+# default for csharp files.
+# Note: This is only used by command line
+###############################################################################
+#*.cs     diff=csharp
+
+###############################################################################
+# Set the merge driver for project and solution files
+#
+# Merging from the command prompt will add diff markers to the files if there
+# are conflicts (Merging from VS is not affected by the settings below, in VS
+# the diff markers are never inserted). Diff markers may cause the following 
+# file extensions to fail to load in VS. An alternative would be to treat
+# these files as binary and thus will always conflict and require user
+# intervention with every merge. To do so, just uncomment the entries below
+###############################################################################
+#*.sln       merge=binary
+#*.csproj    merge=binary
+#*.vbproj    merge=binary
+#*.vcxproj   merge=binary
+#*.vcproj    merge=binary
+#*.dbproj    merge=binary
+#*.fsproj    merge=binary
+#*.lsproj    merge=binary
+#*.wixproj   merge=binary
+#*.modelproj merge=binary
+#*.sqlproj   merge=binary
+#*.wwaproj   merge=binary
+
+###############################################################################
+# behavior for image files
+#
+# image files are treated as binary by default.
+###############################################################################
+#*.jpg   binary
+#*.png   binary
+#*.gif   binary
+
+###############################################################################
+# diff behavior for common document formats
+# 
+# Convert binary document formats to text before diffing them. This feature
+# is only available from the command line. Turn it on by uncommenting the 
+# entries below.
+###############################################################################
+#*.doc   diff=astextplain
+#*.DOC   diff=astextplain
+#*.docx  diff=astextplain
+#*.DOCX  diff=astextplain
+#*.dot   diff=astextplain
+#*.DOT   diff=astextplain
+#*.pdf   diff=astextplain
+#*.PDF   diff=astextplain
+#*.rtf   diff=astextplain
+#*.RTF   diff=astextplain

.github/CONTRIBUTING.md

@@ -0,0 +1,46 @@
+# Contributing
+
+First off, thanks for taking the time to contribute!
+
+### How can I contribute?
+
+* Fork this project;
+* Make your changes / new implementatios;
+* Use the pattern for git commts; 
+* Make sure that the acceptance criteria are met (tests, docs, etc);
+* Create a pull request;
+
+### Pull Requests
+
+Template [PULLREQUEST-TEMPLATE](PULLREQUEST-TEMPLATE.md)
+
+### Git Commit Messages
+
+* Use the present tense ("Adds feature" not "Added feature")
+* Limit the first line to 72 characters or less
+* Reference issues and pull requests liberally
+* Consider starting the commit message with an applicable emoji:
+    * :art: `:art:` when improving the format/structure of the code
+    * :racehorse: `:racehorse:` when improving performance
+    * :non-potable_water: `:non-potable_water:` when plugging memory leaks
+    * :memo: `:memo:` when writing docs
+    * :penguin: `:penguin:` when fixing something on Linux
+    * :apple: `:apple:` when fixing something on Mac OS
+    * :checkered_flag: `:checkered_flag:` when fixing something on Windows
+    * :bug: `:bug:` when fixing a bug
+    * :fire: `:fire:` when removing code or files
+    * :green_heart: `:green_heart:` when fixing the CI build
+    * :white_check_mark: `:white_check_mark:` when adding tests
+    * :lock: `:lock:` when dealing with security
+    * :arrow_up: `:arrow_up:` when upgrading dependencies
+    * :arrow_down: `:arrow_down:` when downgrading dependencies
+    * :shirt: `:shirt:` when removing linter warnings
+    * :bulb: `:bulb:` new idea
+    * :construction: `:construction:` work in progress
+    * :heavy_plus_sign: `:heavy_plus_sign:` when adding features
+    * :heavy_minus_sign: `:heavy_minus_sign:` when removing features
+    * :speaker: `:mute:` when adding logging
+    * :mute: `:mute:` when reducing logging
+    * :facepunch: `:facepunch:` when resolve conflict
+    * :wrench: `:wrench:` when modify Web.config
+

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,43 @@
+```
+Please use the following template to submit your issue. 
+Following this template will allow us to quickly investigate and help you with your issue. 
+Please be aware that issues which do not conform to this template may be closed. 
+
+DO NOT FORGET TO REMOVE THIS BLOCK
+```
+
+### Status
+
+BUG REPORT / TASK
+
+### Checklist
+
+Add checklist if this is a task
+
+- [x] Add slack integration
+- [_] Support xyz 
+
+### Steps
+
+1. First step
+2. Second step
+3. Third step
+
+### Expected behaviour
+
+How do you think the program should work? Add screenshots and code blocks if necessary.
+
+### Actual behaviour
+
+How does the program work in its current state?
+
+### Environment
+
+You may write here the specifications like the version of the project, services, operating system, or hardware if applicable.
+
+### Logs / Stack trace
+
+```
+Insert your log/stack trace here
+```
+

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,44 @@
+```
+This is a guide to use this Pull Request Template.
+
+# Title
+[feature] Implements the crazy powerful transaction search
+[hotfix] Fixes login with e-mail address
+
+Add a gif that expresses your reaction to the implemented code, make it fun
+
+DO NOT FORGET TO REMOVE THIS BLOCK
+```
+![Git Merge](https://media.giphy.com/media/cFkiFMDg3iFoI/giphy.gif)
+
+### Status
+
+READY / IN DEVELOPMENT
+
+### Whats?
+
+Describe in an objective way what has been done.
+
+### Why?
+
+Why do you need this implementation/fix? 
+
+### How?
+
+How did you solve the problem? What are the main flows? Any technical information regarding infrastructure or architecture?
+
+### Attachments (if appropriate)
+
+Add additional informations like screenshots, issue link, zendesk ticket link, jira task link, etc
+
+### Definition of Done:
+- [ ] Increases API documentation
+- [ ] Implements integration tests
+- [ ] Implements unit tests
+- [ ] Is there appropriate logging included?
+- [ ] Does this add new dependencies?
+- [ ] Does need add new version in changelog?
+- [ ] Does need update readme, contributing, etc?
+- [ ] Does need change in CI server?
+- [ ] Will this feature require a new piece of infrastructure be implemented?
+- [ ] Does this PR require a blog post? If so, ensure marketing has signed off on content.