Merge pull request #2 from hyperledger/maintainers

Add MAINTAINERS.md and standard repo files

CHANGELOG.md

@@ -0,0 +1,3 @@
+# Changelog
+
+See [Hyperledger FireFly Releases](https://github.com/hyperledger/firefly/releases)

CODEOWNERS

@@ -0,0 +1,3 @@
+# SPDX-License-Identifier: Apache-2.0
+
+- @hyperledger/firefly-tezosconnect-maintainers

CODE_OF_CONDUCT.md

@@ -0,0 +1,7 @@
+# Code of Conduct Guidelines
+
+Please review the Hyperledger [Code of
+Conduct](https://wiki.hyperledger.org/community/hyperledger-project-code-of-conduct)
+before participating. It is important that we keep things civil.
+
+<a rel="license" href="http://creativecommons.org/licenses/by/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by/4.0/88x31.png" /></a><br />This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</a>.

MAINTAINERS.md

@@ -0,0 +1,12 @@
+# firefly-core-maintainers
+
+The following is the list of current maintainers this repo:
+
+| Name               | GitHub         | Email                               | LFID   |
+| ------------------ | -------------- | ----------------------------------- | ------ |
+| Dzianis Andreyenka | denisandreenko | [email protected] | Darus  |
+| Nicko Guyer        | nguyer         | [email protected]              | nguyer |
+
+This list is to be kept up to date as maintainers are added or removed.
+
+For the full list of maintainers across all repos, the expectations of a maintainer and the process for becoming a maintainer, please see the [FireFly Maintainers page on the Hyperledger Wiki](https://wiki.hyperledger.org/display/FIR/Maintainers).

SECURITY.md

@@ -0,0 +1,20 @@
+# Hyperledger Security Policy
+
+## Reporting a Security Bug
+
+If you think you have discovered a security issue in any of the Hyperledger projects, we'd love to
+hear from you. We will take all security bugs seriously and if confirmed upon investigation we will
+patch it within a reasonable amount of time and release a public security bulletin discussing the
+impact and credit the discoverer.
+
+There are two ways to report a security bug. The easiest is to email a description of the flaw and
+any related information (e.g. reproduction steps, version) to
+[security at hyperledger dot org](mailto:[email protected]).
+
+The other way is to file a confidential security bug in our
+[JIRA bug tracking system](https://jira.hyperledger.org). Be sure to set the “Security Level” to
+“Security issue”.
+
+The process by which the Hyperledger Security Team handles security bugs is documented further in
+our [Defect Response page](https://wiki.hyperledger.org/display/SEC/Defect+Response) on our
+[wiki](https://wiki.hyperledger.org).