Update Governance and Code of Conduct verbiage. (#120)

The old governance doc does not apply to the Hyperledger project, so it
is deleted.

Added a note that there is also a HLP code of conduct that also applies.

Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>

CONTRIBUTING.md

@@ -29,6 +29,14 @@ and feel free to propose changes to this document in a pull request.
 This project and everyone participating in it is governed by the [Besu Code of Conduct](CODE-OF-CONDUCT.md).
 By participating, you are expected to uphold this code. Please report unacceptable behavior to [private@pegasys.tech].
 
+The [Hyperledger Code of Conduct](https://wiki.hyperledger.org/community/hyperledger-project-code-of-conduct) 
+also applies to participants in this project.
+
+## Governance
+
+Hyperledger Besu is managed under an open governance model as described in the [HyperLedger 
+charter](https://www.hyperledger.org/about/charter). Hyperledger Besu is lead by a set of [maintainers](MAINTAINERS.md).
+
 ## I just have a quick question
 
 > **Note:** Please don't file an issue to ask a question.  You'll get faster results by using the resources below.

GOVERNANCE.md

@@ -1,39 +0,0 @@
-# Overview
-This project is led by a benevolent dictator (PegaSys) and managed by the community. That is, the community actively contributes to the day-to-day maintenance of the project, but the general strategic line is drawn by the benevolent dictator. In case of disagreement, they have the last word. It is the benevolent dictator’s job to resolve disputes within the community and to ensure that the project is able to progress in a coordinated way. In turn, it is the community’s job to guide the decisions of the benevolent dictator through active engagement and contribution.
-
-
-# Principles
-
-The community adheres to the following principles:
-* Open: Besu is open source. See repository guidelines and CLA, below.
-* Welcoming and respectful: See Code of Conduct, below.
-* Transparent and accessible: Work and collaboration should be done in public. 
-* Merit: Ideas and contributions are accepted according to their technical merit and alignment with project objectives and design principles.
-
-# Code of Conduct
-See [code of conduct]
-
-# Community membership
-
-See [community membership]
-
-# Decision Making
-Decision making will be handled by the Approvers (see [community membership]).  If consensus cannot be reached, the Benevolent Dictator will provide the final word on the decision.
-
-
-# DCO
-
-All contributors must send commits with sign-off to comply with [DCO](DCO.md)
-## Attribution
-
-This document was influenced by the following:
-- Kubernetes community-membership.md, available at [kub community membership].
-- Kubernetes governance.md, available at [kub governance]  
-- OSSWatch Benevolent Dictator Governance Model, available at [oss watch benevolent dictator].  
-
-[CLA.md]: /CLA.md
-[community membership]: /docs/community/community-membership.md 
-[code of conduct]: /CODE-OF-CONDUCT.md
-[oss watch benevolent dictator]: http://oss-watch.ac.uk/resources/benevolentdictatorgovernancemodel
-[kub community membership]: https://raw.githubusercontent.com/kubernetes/community/master/community-membership.md
-[kub governance]:https://github.com/kubernetes/community/blob/master/governance.md