Merge quorum 'master'

.bintray.json

@@ -0,0 +1,37 @@
+{
+  "package": {
+    "name": "geth",
+    "repo": "quorum",
+    "subject": "_ORGANIZATION_",
+    "vcs_url": "https://github.com/jpmorganchase/quorum",
+    "licenses": [
+      "LGPL-3.0"
+    ]
+  },
+  "version": {
+    "name": "_TRAVIS_TAG_",
+    "desc": "Quorum: _TRAVIS_TAG_, Geth: _GETH_VERSION_, Commit: _TRAVIS_COMMIT_, Build Number: _TRAVIS_BUILD_NUMBER_",
+    "released": "_RELEASED_DATE_",
+    "vcs_tag": "_TRAVIS_TAG_",
+    "gpgSign": true,
+    "attributes": [
+      {
+        "name": "Travis",
+        "values": [
+          "_TRAVIS_JOB_WEB_URL_"
+        ],
+        "type": "string"
+      }
+    ]
+  },
+  "files": [
+    {
+      "includePattern": "/dist/(.*.tar.gz)",
+      "uploadPattern": "_TRAVIS_TAG_/$1",
+      "matrixParams": {
+        "override": 1
+      }
+    }
+  ],
+  "publish": true
+}

.github/CONTRIBUTING.md

@@ -1,40 +1,42 @@
 # Contributing
 
-Thank you for considering to help out with the source code! We welcome 
-contributions from anyone on the internet, and are grateful for even the 
+Thank you for your interest in contributing to GoQuorum!
+
+We welcome contributions from anyone on the internet, and are grateful for even the
 smallest of fixes!
 
-If you'd like to contribute to go-ethereum, please fork, fix, commit and send a 
-pull request for the maintainers to review and merge into the main code base. If
-you wish to submit more complex changes though, please check up with the core 
-devs first on [our gitter channel](https://gitter.im/ethereum/go-ethereum) to 
-ensure those changes are in line with the general philosophy of the project 
-and/or get some early feedback which can make both your efforts much lighter as
-well as our review and merge procedures quick and simple.
+If you'd like to contribute to quorum please fork, fix, commit and
+send a pull request. Commits which do not comply with the coding standards
+are ignored.
 
 ## Coding guidelines
 
 Please make sure your contributions adhere to our coding guidelines:
 
- * Code must adhere to the official Go 
-[formatting](https://golang.org/doc/effective_go.html#formatting) guidelines 
+ * Code must adhere to the official Go
+[formatting](https://golang.org/doc/effective_go.html#formatting) guidelines
 (i.e. uses [gofmt](https://golang.org/cmd/gofmt/)).
- * Code must be documented adhering to the official Go 
+ * Code must be documented adhering to the official Go
 [commentary](https://golang.org/doc/effective_go.html#commentary) guidelines.
  * Pull requests need to be based on and opened against the `master` branch.
  * Commit messages should be prefixed with the package(s) they modify.
    * E.g. "eth, rpc: make trace configs optional"
 
 ## Can I have feature X
 
-Before you submit a feature request, please check and make sure that it isn't 
-possible through some other means. The JavaScript-enabled console is a powerful 
-feature in the right hands. Please check our 
-[Geth documentation page](https://geth.ethereum.org/docs/) for more info
+Before you submit a feature request, please check and make sure that it isn't
+possible through some other means. The JavaScript-enabled console is a powerful
+feature in the right hands. Please check our
+[developer documentation](https://docs.goquorum.consensys.net/en/latest/) for more info
 and help.
 
 ## Configuration, dependencies, and tests
 
 Please see the [Developers' Guide](https://geth.ethereum.org/docs/developers/devguide)
 for more details on configuring your environment, managing project dependencies
 and testing procedures.
+
+## Issue reproductibility
+
+Before you create an issue, please try to reproduce it with [quorum quick dev start framework](https://github.com/ConsenSys/quorum-dev-quickstart) with the latest release.
+Many issues have been creating under an environment we are not able to reproduce quickly.

.github/dependabot.yml

@@ -0,0 +1,11 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+
+version: 2
+updates:
+  - package-ecosystem: gomod
+    directory: /
+    schedule:
+      interval: daily