diff --git a/.azure-pipelines/build-template.yml b/.azure-pipelines/build-template.yml
index 41f344a..898e60a 100644
--- a/.azure-pipelines/build-template.yml
+++ b/.azure-pipelines/build-template.yml
@@ -51,7 +51,29 @@ jobs:
       runVersion: 'latestFromBranch'
       runBranch: 'refs/heads/master'
     displayName: "Download sonic swss common deb packages"
-
+    
+  - task: DownloadPipelineArtifact@2
+    inputs:
+      source: specific
+      project: build
+      pipeline: Azure.sonic-buildimage.common_libs
+      runVersion: 'latestFromBranch'
+      runBranch: 'refs/heads/master'
+      path: $(Build.ArtifactStagingDirectory)/download
+      ${{ if eq(parameters.arch, 'amd64') }}:
+        artifact: common-lib
+      ${{ else }}:
+        artifact: common-lib.${{ parameters.arch }}
+      patterns: |
+        target/debs/buster/libyang-*.deb
+        target/debs/buster/libyang_*.deb
+    displayName: "Download libyang from common lib"
+    
+  - script: |
+      set -ex
+      sudo dpkg -i $(find ./download -name *.deb)
+    workingDirectory: $(Build.ArtifactStagingDirectory)
+    displayName: "Install libyang from common lib"
   - script: |
       set -ex
       pwd
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..91f03eb
--- /dev/null
+++ b/README.md
@@ -0,0 +1,45 @@
+# sonic-stp
+
+## Description
+Contains source code for the implementation of SONiC PVSTP. Based on the HLD https://github.com/sonic-net/SONiC/blob/master/doc/stp/SONiC_PVST_HLD.md
+
+## Contribution guide
+
+See the [contributors guide](https://github.com/sonic-net/SONiC/wiki/Becoming-a-contributor) for information about how to contribute.
+
+All contributors must sign an [Individual Contributor License Agreement (ICLA)](https://docs.linuxfoundation.org/lfx/easycla/v2-current/contributors/individual-contributor) before 
+contributions can be accepted. This process is managed by the [Linux Foundation - EasyCLA](https://easycla.lfx.linuxfoundation.org/) and automated
+via a GitHub bot. If the contributor has not yet signed a CLA, the bot will create a comment on the pull request containing a link to electronically sign the CLA.
+
+### GitHub Workflow
+
+We're following basic GitHub Flow. If you have no idea what we're talking about, check out [GitHub's official guide](https://guides.github.com/introduction/flow/). Note that merge is only performed by the repository maintainer.
+
+Guide for performing commits:
+
+* Isolate each commit to one component/bugfix/issue/feature
+* Use a standard commit message format:
+
+>     [component/folder touched]: Description intent of your changes
+>
+>     [List of changes]
+>
+> 	  Signed-off-by: Your Name your@email.com
+
+For example:
+
+>     swss-common: Stabilize the ConsumerTable
+>
+>     * Fixing autoreconf
+>     * Fixing unit-tests by adding checkers and initialize the DB before start
+>     * Adding the ability to select from multiple channels
+>     * Health-Monitor - The idea of the patch is that if something went wrong with the notification channel,
+>       we will have the option to know about it (Query the LLEN table length).
+>
+>       Signed-off-by: user@dev.null
+
+
+* Each developer should fork this repository and [add the team as a Contributor](https://help.github.com/articles/adding-collaborators-to-a-personal-repository)
+* Push your changes to your private fork and do "pull-request" to this repository
+* Use a pull request to do code review
+* Use issues to keep track of what is going on