Getting all latest commits from the original branch

.gitattributes

@@ -12,6 +12,7 @@
 
 # Declare files that will always have LF line endings on checkout. E.g.,
 *.sh text eol=lf
+*.json text eol=lf
 
 # Denote all files that should not have line endings normalized, should not be
 # merged, and should not show in a textual diff.

.github/CONTRIBUTING.md

@@ -0,0 +1,65 @@
+**The Azure IoT SDKs team wants to hear from you!**
+
+- [Ask a question](#ask-a-question)
+- [File a bug](#file-a-bug)
+- [Contribute documentation](#contribute-documentation)
+- [Contribute code](#contribute-code)
+
+# Ask a question
+Our team monitors Stack Overflow, especially the [azure-iot-hub](http://stackoverflow.com/questions/tagged/azure-iot-hub) tag. It really is the best place to ask.
+
+We monitor the Github issues section specifically for bugs found with our SDK, however we will reply to questions asked using Github issues too.
+
+# File a bug (code or documentation)
+That is definitely something we want to hear about. Please open an issue on github, we'll address it as fast as possible. Typically here's the information we're going to ask for to get started:
+- What SDK are you using (Node, C, C#, Python, Java?)
+- What version of the SDK?
+- Do you have a snippet of code that would help us reproduce the bug?
+- Do you have logs showing what's happening?
+
+Our SDK is entirely open-source and we do accept pull-requests if you feel like taking a stab at fixing the bug and maybe adding your name to our commit history :) Please mention
+any relevant issue number in the pull request description.
+
+# Contribute documentation
+For simple markdown files, we accept documentation pull requests submitted against the `master` branch, if it's about existing SDK features.
+If your PR is about future changes or has changes to the comments in the code itself, we'll treat is as a code change (see the next section).
+
+# Contribute code
+Unlike documentation, we require pull-requests for code to be submitted against the `develop` branch in order to review and run it in our gated build system. We try to maintain a high bar
+for code quality and maintainability, we insist on having tests associated with the code, and if necessary, additions/modifications to the requirement documents.
+
+Also, have you signed the [Contribution License Agreement](https://cla.microsoft.com/) ([CLA](https://cla.microsoft.com/))? A friendly bot will remind you about it when you submit your pull-request.
+
+If you feel like your contribution is going to be a major effort, you should probably give us a heads-up. We have a lot of items captured in our backlog and we release every two weeks, so before you spend the time, just check with us to make
+sure your plans and ours are in sync :) Just open an issue on github and tag it "enhancement" or "feature request"
+
+## Editing module requirements
+We use requirement documents to describe the expected behavior for each code modules. It works as a basis to understand what tests need to be written.
+
+Each requirement has a unique tag that is re-used in the code comments to identify where it's implemented and where it's tested. To generate these unique identifiers, we used to use a Microsoft Word macro.
+We are progressively switching to Markdown though, for which we have no macro, therefore we have to be careful about numbering.
+
+The following steps describe adding a new requirement in a Word document:
+
+* Add the requirement text and select it
+
+![](media/add_requirement/add_requirement_step1.png)
+
+* Invoke the macro with the selected text
+
+![](media/add_requirement/add_requirement_step2.png)
+
+* Select developer id 99
+
+![](media/add_requirement/add_requirement_step3.png)
+
+* Done!
+
+![](media/add_requirement/add_requirement_step4.png)
+
+When contributing to markdown requirement docs, you can also use `99` for a developer id, and just increment the last number of the requirement to be unique.
+
+## Adding new files
+If your contribution is not part of an already existed code, you must create a new requirement file and a new unit test project. Our team created a template to help you on it. For the requirements you can copy the [template_requirements.md](https://github.com/Azure/azure-c-shared-utility/blob/develop/devdoc/template_requirements.md) to the appropriate `devdoc` directory and change it to fits your needs.
+
+For the unit test, copy the directory [template_ut](https://github.com/Azure/azure-c-shared-utility/tree/develop/tests/template_ut) to the appropriate `tests` directory and change it to fits your needs. To include your new test suite in the `cmake`, add your new test suite in `test/CMakeLists.txt` with the command `add_subdirectory(template_ut)`.

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,25 @@
+<!--
+Hi there! Thank you for discovering and submitting an issue.
+
+Before your submit it though, please consider that each Azure IoT SDK now lives in its own repository. You can follow this link to create a new issue for a specific SDK:
+- C:      https://github.com/azure/azure-iot-sdk-c/issues/new
+- .NET:   https://github.com/azure/azure-iot-sdk-csharp/issues/new
+- Node:   https://github.com/azure/azure-iot-sdk-node/issues/new
+- Java:   https://github.com/azure/azure-iot-sdk-java/issues/new
+- Python: https://github.com/azure/azure-iot-sdk-python/issues/new
+
+It's going to be a lot easier for us to track and link your issue to its resolution (commit hash, etc) in the concerned SDK repository directly.
+
+If you think the issue you discovered belongs here more than in any specific SDK repository, please consider the following list of questions that will help us debug the issue:
+--> 
+
+- SDK used when observing the issue: <!-- Please include the SDK language and version -->
+- Type of device: <!-- PC, Mac, Raspberry Pi, Arduino... -->
+- OS (with version) on which the code is running <!-- Ubuntu 15.04, Windows 10... -->
+
+
+Code sample exhibiting the issue: <!-- Please do not leave any connection string details in here -->
+
+
+Console log of the issue: <!-- Please do not leave any connection string details in here either -->
+

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,15 @@
+<!--
+Hi there! Thank you for your interest in the Azure IoT SDKs
+
+Before you create a pull request though, please consider that each Azure IoT SDK now lives in its own repository:
+- C:      https://github.com/azure/azure-iot-sdk-c
+- .NET:   https://github.com/azure/azure-iot-sdk-csharp
+- Node:   https://github.com/azure/azure-iot-sdk-node
+- Java:   https://github.com/azure/azure-iot-sdk-java
+- Python: https://github.com/azure/azure-iot-sdk-python
+
+We will not be accepting pull-requests for SDK code in this repository, and encourage you to clone the specific SDK repository and submit your PR there. 
+Please remember that all code pull-requests must include tests and be submitted against the `develop` branch
+
+Thank you again, we appreciate all feedback!
+--> 

.gitignore

@@ -20,6 +20,9 @@
 x64/
 [Bb]in/
 [Oo]bj/
+/build/release/Maven
+!/build/release/
+[Cc]make/
 
 # Enable "build/" folder in the NuGet Packages folder since NuGet packages use it for MSBuild targets
 !packages/*/build/
@@ -71,6 +74,7 @@ ipch/
 # ReSharper is a .NET coding add-in
 _ReSharper*/
 *.[Rr]e[Ss]harper
+*.VC.opendb
 
 # TeamCity is a build add-in
 _TeamCity*
@@ -122,6 +126,7 @@ ClientBin/
 *.[Pp]ublish.xml
 *.pfx
 *.publishsettings
+*.jar
 
 # RIA/Silverlight projects
 Generated_Code/
@@ -143,6 +148,12 @@ GeneratedArtifacts/
 _Pvt_Extensions/
 ModelManifest.xml
 
+# CPython & Wheels
+*.pyc
+*.pyd
+*.whl
+*.egg-info
+
 # =========================
 # Windows detritus
 # =========================
@@ -168,6 +179,9 @@ $RECYCLE.BIN/
 *.lib
 *.dll
 
+# Visual Studio Temporary files
+*.VC.db
+
 # Windows CE build artifacts
 Build.err
 Build.wrn
@@ -186,28 +200,40 @@ java/**/out/
 java/**/target/
 java/**/*.iml
 java/**/*dependency-reduced-pom.xml
+java/**/*.crt
 
 # Node.js
 **/.settings/
 **/node_modules/
 **/.idea/
+**/coverage/
 
 # VS Code stuff
 **/typings/**
 **/.vscode/**
+# C/C++ extension for VS Code
+.browse.VC.db*
 
-csharp/device/NuGet/*.exe
-csharp/device/NuGet/*.nupkg
-csharp/device/.vs/*
 service/java/.idea
 service/java/target
 service/java/iot.service.sdk.java.iml
 java/device/doc/api_reference
 java/service/doc/api_reference
 c/build_all/windows/nuget.exe
-csharp/device/build/nuget.exe
 
 # .NET Micro Framework Emulator files and folders
 OnBoardFlash.dat
 OnBoardFlash.dat.smd
 DOTNETMF_FS_EMULATION*/
+/c/cmake
+/c/build
+javawrapper/device/iothub_client_javawrapper/target
+javawrapper/device/samples/direct_call_of_wrapped_functions/target
+javawrapper/device/samples/send-receive-sample/target
+javawrapper/device/samples/send-serialized-event/target
+javawrapper/device/samples/file-upload-sample/target
+javawrapper/device/samples/send-event-sample/target
+javawrapper/device/test/target
+javawrapper/device/samples/target
+*.so
+python/build_all/windows/pyenv.bat

SECURITY.md

@@ -0,0 +1,41 @@
+<!-- BEGIN MICROSOFT SECURITY.MD V0.0.8 BLOCK -->
+
+## Security
+
+Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/).
+
+If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/opensource/security/definition), please report it to us as described below.
+
+## Reporting Security Issues
+
+**Please do not report security vulnerabilities through public GitHub issues.**
+
+Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report).
+
+If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com).  If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/opensource/security/pgpkey).
+
+You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc). 
+
+Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
+
+  * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
+  * Full paths of source file(s) related to the manifestation of the issue
+  * The location of the affected source code (tag/branch/commit or direct URL)
+  * Any special configuration required to reproduce the issue
+  * Step-by-step instructions to reproduce the issue
+  * Proof-of-concept or exploit code (if possible)
+  * Impact of the issue, including how an attacker might exploit the issue
+
+This information will help us triage your report more quickly.
+
+If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs.
+
+## Preferred Languages
+
+We prefer all communications to be in English.
+
+## Policy
+
+Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/opensource/security/cvd).
+
+<!-- END MICROSOFT SECURITY.MD BLOCK -->

azure-pipelines.yml

@@ -0,0 +1,19 @@
+# Starter pipeline
+# Start with a minimal pipeline that you can customize to build and deploy your code.
+# Add steps that build, run tests, deploy, and more:
+# https://aka.ms/yaml
+
+trigger:
+- master
+
+pool:
+  vmImage: ubuntu-latest
+
+steps:
+- script: echo Hello, world!
+  displayName: 'Run a one-line script'
+
+- script: |
+    echo Add other tasks to build, test, and deploy your project.
+    echo See https://aka.ms/yaml
+  displayName: 'Run a multi-line script'