Skip to content

Update docs links #704

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yeasy merged 9 commits into from
Jul 7, 2025
+6 −12
Merged

Update docs links #704

Show file tree
Hide file tree
Changes from 8 commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
c89002b
Fix broken code of conduct link
dodo920306 Jun 29, 2025
80d315f
Bump the npm_and_yarn group across 1 directory with 3 updates
dependabot[bot] Jun 29, 2025
4964708
Update references in index.md
dodo920306 Jun 29, 2025
93f73b6
Merge branch 'main' into fix/broken-code-of-conduct-ref
dodo920306 Jun 29, 2025
d9350f0
Update links to report security issues
dodo920306 Jun 29, 2025
8e63f97
Prevent reporting vulnerabilities as GitHub issues
dodo920306 Jul 1, 2025
f626365
Make Hackerone as the way to report vulnerabilities
dodo920306 Jul 1, 2025
13493d1
Merge branch 'main' into fix/broken-code-of-conduct-ref
yeasy Jul 5, 2025
c1e65d3
Merge branch 'main' into fix/broken-code-of-conduct-ref
yeasy Jul 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions CODE_OF_CONDUCT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.

<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>.
7 changes: 2 additions & 5 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:[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/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).
7 changes: 3 additions & 4 deletions docs/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Copy link
Contributor

@yeasy yeasy Jul 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are not using discord now. So better remove this line.

* [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.

<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>.