Welcome 😊

.github/issue_template.md

@@ -0,0 +1,5 @@
+1. Expected behavior and actual behavior.
+
+2. Steps to reproduce the problem.
+
+3. Specifications like the version of the project, operating system, or hardware.

.gitignore

@@ -0,0 +1,88 @@
+
+# Created by https://www.gitignore.io/api/gradle,intellij+all
+
+### Intellij+all ###
+# Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio and Webstorm
+# Reference: https://intellij-support.jetbrains.com/hc/en-us/articles/206544839
+
+# User-specific stuff:
+.idea/**/workspace.xml
+.idea/**/tasks.xml
+.idea/dictionaries
+
+# Sensitive or high-churn files:
+.idea/**/dataSources/
+.idea/**/dataSources.ids
+.idea/**/dataSources.xml
+.idea/**/dataSources.local.xml
+.idea/**/sqlDataSources.xml
+.idea/**/dynamic.xml
+.idea/**/uiDesigner.xml
+
+# Gradle:
+.idea/**/gradle.xml
+.idea/**/libraries
+
+# CMake
+cmake-build-debug/
+
+# Mongo Explorer plugin:
+.idea/**/mongoSettings.xml
+
+## File-based project format:
+*.iws
+
+## Plugin-specific files:
+
+# IntelliJ
+/out/
+
+# mpeltonen/sbt-idea plugin
+.idea_modules/
+
+# JIRA plugin
+atlassian-ide-plugin.xml
+
+# Cursive Clojure plugin
+.idea/replstate.xml
+
+# Ruby plugin and RubyMine
+/.rakeTasks
+
+# Crashlytics plugin (for Android Studio and IntelliJ)
+com_crashlytics_export_strings.xml
+crashlytics.properties
+crashlytics-build.properties
+fabric.properties
+
+### Intellij+all Patch ###
+# Ignores the whole idea folder
+# See https://github.com/joeblau/gitignore.io/issues/186 and https://github.com/joeblau/gitignore.io/issues/360
+
+.idea/
+
+### Gradle ###
+.gradle
+**/build/
+
+# Ignore Gradle GUI config
+gradle-app.setting
+
+# Avoid ignoring Gradle wrapper jar file (.jar files are usually ignored)
+!gradle-wrapper.jar
+
+# Cache of project
+.gradletasknamecache
+
+# # Work around https://youtrack.jetbrains.com/issue/IDEA-116898
+# gradle/wrapper/gradle-wrapper.properties
+
+# End of https://www.gitignore.io/api/gradle,intellij+all
+.vertx/
+
+buffers/out
+crypto/out
+
+gradle-local.properties
+
+bin/

CHANGELOG.md

@@ -0,0 +1,2 @@
+# CHANGELOG
+

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,85 @@
+# Contributing to nem2-sdk-java
+
+First off, thank you for considering contributing to nem2-sdk-java. 
+It’s people like you that make nem2-sdk-java such a great tool.
+
+nem2-sdk-java is an open source project and we love to receive contributions from 
+our community — you! There are many ways to contribute, from writing tutorials or blog 
+posts, improving the documentation, submitting bug reports and feature requests or 
+writing code which can be incorporated into nem2-sdk-java itself.
+
+Following these guidelines helps to communicate that you respect the time of 
+the developers managing and developing this open source project. In return, 
+they should reciprocate that respect in addressing your issue, assessing changes, 
+and helping you finalize your pull requests.
+
+Please, **don't use the issue tracker for support questions**. 
+
+## Bug reports
+
+If you think you have found a bug in nem2-sdk-java, first make sure that you 
+are testing against the latest version of nem2-sdk-java - your issue may already 
+have been fixed. If not, search our issues list on GitHub in case a similar 
+issue has already been opened.
+
+It is very helpful if you can prepare a reproduction of the bug. In other words, 
+provide a small test case which we can run to confirm your bug. It makes it easier to 
+find the problem and to fix it.
+
+Please, take in consideration the next template to report your issue:
+
+> **Expected Behaviour**\
+> Short and expressive sentence explaining what the code should do.\
+> **Current Behaviour**\
+> A short sentence enplaning what the code does. \
+> **Steps to reproduce**\
+> For faster issue detection, we would need a step by step description do reproduce the issue.
+
+
+Provide as much information as you can.
+
+Open a new issue [here][github-issues].
+
+## Feature requests
+
+If you find yourself wishing for a feature that doesn't exist in nem2-sdk-java, 
+you are probably not alone. There are bound to be others out there with similar 
+needs. Many of the features that nem2-sdk-java has today have been added because 
+our users saw the need. Open an [issue][github-issues] on our issues list on GitHub which describes 
+the feature you would like to see, why you need it, and how it should work.
+
+## Contributing code and documentation changes
+
+If you have a bugfix or new feature that you would like to contribute to Elasticsearch, please find or open an issue 
+about it first. Talk about what you would like to do. It may be that somebody is already working on it, or that there 
+are particular issues that you should know about before implementing the change.
+
+We enjoy working with contributors to get their code accepted. There are many approaches to fixing a problem and it is 
+important to find the best approach before writing too much code.
+
+### Fork and clone the repository
+
+You will need to fork the main nem2-sdk-java code or documentation repository and clone 
+it to your local machine. See [github help page](https://help.github.com/articles/fork-a-repo/) for help.
+
+Further instructions for specific projects are given below.
+
+### Submitting your changes
+
+Once your changes and tests are ready to submit for review:
+
+1. Test your changes
+
+    Run the test suite to make sure that nothing is broken.
+
+2. Submit a pull request
+
+    Push your local changes to your forked copy of the repository and [submit a pull request](https://help.github.com/articles/about-pull-requests/). In the pull request, choose a title which sums up the changes that you have made, and in the body provide more details about what your changes do. Also mention the number of the issue where discussion has taken place, eg "Closes #123".
+
+Then sit back and wait. There will probably be discussion about the pull request and, if any changes are needed, we would love to work with you to get your pull request merged into nem2-sdk-java.
+
+*CONTRIBUTING.md is based on [CONTRIBUTING-template.md](https://github.com/nayafia/contributing-template/blob/master/CONTRIBUTING-template.md)* 
+and [elasticsearch/CONTRIGUTING](https://github.com/elastic/elasticsearch/blob/master/CONTRIBUTING.md)
+
+[pull-request]: https://help.github.com/articles/about-pull-requests/
+[github-issues]: https://github.com/nemtech/nem2-sdk-java/issues