diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index 339bf98f4..f2c740f13 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -1,8 +1,6 @@ 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. +Please review the Hyperledger [Code of Conduct](https://hyperledger.github.io/governance/code-of-conduct.html) before participating. It is important that we keep things civil. Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License. \ No newline at end of file diff --git a/SECURITY.md b/SECURITY.md index 91509aa05..53beb8bf1 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -4,9 +4,6 @@ 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:security@hyperledger.org). - -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/HYP/Defect+Response) on our [wiki](https://wiki.hyperledger.org). +To report a security bug, please submit it via [Hackerone](https://hackerone.com/hyperledger?type=team). +The process by which the Hyperledger Security Team handles security bugs is documented further in our [Defect Response page](https://lf-hyperledger.atlassian.net/wiki/spaces/SEC/pages/20283618/Defect+Response) on our [wiki](https://lf-hyperledger.atlassian.net/wiki). diff --git a/docs/index.md b/docs/index.md index 73de1ea25..45201f47f 100644 --- a/docs/index.md +++ b/docs/index.md @@ -39,11 +39,10 @@ Using Cello, blockchain developers can: For additional helps, feel free to take the following channels: -* [Wikipage](https://wiki.hyperledger.org/projects/cello): Lots of information and documentation about the project, e.g., meeting schedule, design doc. -* [Mail List](mailto:hyperledger-cello@lists.hyperledger.org): General technical topics with Cello project. +* [Wikipage](https://lf-hyperledger.atlassian.net/wiki/spaces/cello/overview): Lots of information and documentation about the project, e.g., meeting schedule, design doc. +* [Mail List](mailto:cello@lists.lfdecentralizedtrust.org): General technical topics with Cello project. * [Discord](https://discord.gg/hyperledger): Real-time online discussions. -* [Jira Board](https://jira.hyperledger.org/projects/CE/issues): Find development status, report bug, or help [contribute code](contributing.md). -* [GitHub](https://github.com/hyperledger/cello): Development related code and patchsets, welcome to [contribute](contributing.md). +* [GitHub](https://github.com/hyperledger-cello/cello): Development related code and patchsets, welcome to [contribute](contributing.md). * [Stack Overflow](https://stackoverflow.com/questions/tagged/hyperledger-cello): Stack overflow discussion questions about cello. Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.