diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml index ca3f13148..9c1b85a14 100644 --- a/.github/ISSUE_TEMPLATE/config.yml +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -1,8 +1,8 @@ blank_issues_enabled: true contact_links: - - name: Hyperledger Caliper Rocket.Chat channel - url: https://chat.hyperledger.org/channel/caliper - about: Please ask general questions about the project here (LFID required). + - name: Hyperledger Discord + url: https://discord.com/channels/905194001349627914/941417677778473031 + about: Please ask general questions about the project in the Caliper channel (Discord id required). - name: Hyperledger Caliper mailing list url: https://lists.hyperledger.org/g/caliper about: Please ask general questions about the project here (LFID recommended). \ No newline at end of file diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 4e6dceb00..14aa25170 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -8,9 +8,9 @@ If you have further suggestions about improving the guideline, then you can foll ## Overview -The project uses GitHub to manage [issues](https://github.com/hyperledger/caliper/issues) (bug reports and feature requests) and [contributions](https://github.com/hyperledger/caliper/pulls) (in the form of pull requests). +The project uses GitHub to manage [issues](https://github.com/hyperledger/caliper/issues) (bug reports and feature requests) and [contributions](https://github.com/hyperledger/caliper/pulls) (in the form of pull requests). -> For general queries and discussion, please use the [#caliper](https://chat.hyperledger.org/channel/caliper) channel of the Hyperledger Rocket.Chat (LFID required) or the Caliper [mailing list](https://lists.hyperledger.org/g/caliper) (LFID recommended). +> For general queries and discussion, please use the [#caliper](https://discord.com/channels/905194001349627914/941417677778473031) channel on the Hyperledger Discord Server (Discord Id required) or the Caliper [mailing list](https://lists.hyperledger.org/g/caliper) (LFID recommended). The contribution process boils down to two major steps: opening an issue and submitting a pull request (PR). Opening issues before PRs serves the following purposes: * Documenting bugs, related error logs, potential fixes, and/or workarounds that users can find using their favorite search engine. @@ -24,7 +24,7 @@ Opening issues can be omitted only in the case of trivial and small fixes (e.g., Before opening an issue, make sure that: 1. You read the documentation carefully, so the observed error does not stem from incorrect Caliper configuration or usage. 2. You searched older issues (or other forums) for your question, maybe it is already answered/fixed. -3. It is worth to ask around on Rocket.Chat, maybe other users already encountered your issue/task, and managed to solve it. +3. It is worth to ask around on Discord, maybe other users already encountered your issue/task, and managed to solve it. > When opening an issue about a potential bug or feature request, make sure to properly fill and format the issue contents! @@ -44,7 +44,7 @@ The details of the blank template should be filled according to the following gu * The workload module implementation. * The exact error logs (and their surroundings). * Any other information you deem neccessary. -7. **Existing Issues**: You can also provide links to similar (or the same) issues in other forums (GitHub issues, StackOverflow questions or Rocket.Chat messages). Such cross-linking can help us ensure that we can broadcast the potential fixes to multiple instances of the question. +7. **Existing Issues**: You can also provide links to similar (or the same) issues in other forums (GitHub issues, StackOverflow questions or Discord messages). Such cross-linking can help us ensure that we can broadcast the potential fixes to multiple instances of the question. 8. **Your Environment**: Always include your execution environment information, including the used version/commit of Caliper, the operating system, Node.JS version, or any relevant information about your project that uses Caliper. ## Submitting Pull Requests @@ -147,7 +147,7 @@ The [packages/](packages/) directory contains the following internal packages: ## Creating New SUT Connectors -Connectors are relatively heavy components in Caliper. Before you attemp to create a new connector for a new SUT type, consult with the Caliper maintainers (on Rocket.Chat, or in the form of a feature request). +Connectors are relatively heavy components in Caliper. Before you attempt to create a new connector for a new SUT type, consult with the Caliper maintainers (on Discord, or in the form of a feature request). > More importantly, make sure that you are overly familiar with the documentation page about [implementing new connectors](https://hyperledger.github.io/caliper/vNext/writing-connectors/). diff --git a/ISSUE_TEMPLATE.md b/ISSUE_TEMPLATE.md index 82bb4a76f..f870534b8 100644 --- a/ISSUE_TEMPLATE.md +++ b/ISSUE_TEMPLATE.md @@ -24,7 +24,7 @@ - [ ] [Stack Overflow issues](http://stackoverflow.com/tags/hyperledger-caliper) - [ ] [GitHub Issues](https://github.com/hyperledger/caliper/issues) -- [ ] [Rocket Chat history](https://chat.hyperledger.org/channel/caliper) +- [ ] [Discord Chat history](https://discord.com/channels/905194001349627914/941417677778473031) diff --git a/MAINTAINERS.md b/MAINTAINERS.md index b7e00ec94..56b3965dc 100644 --- a/MAINTAINERS.md +++ b/MAINTAINERS.md @@ -1,22 +1,22 @@ Maintainers =========== -The following are lists of the Caliper maintainers, Chat IDs are valid for [Rocket Chat](https://chat.hyperledger.org/channel/caliper) +The following are lists of the Caliper maintainers, Chat IDs are valid for [Discord](https://discord.com/channels/905194001349627914/941417677778473031) **Active maintainers** -| Name | GitHub | Chat | -|---------------------------|------------------|----------------| -| Attila Klenik | aklenik | klenik | -| Nick Lincoln | nklincoln | nkl199 | -| Dave Kelsey | davidkel | davidkel | +| Name | GitHub | Chat | +|---------------------------|------------------|------------------| +| Attila Klenik | aklenik | Attila Klenik | +| Nick Lincoln | nklincoln | | +| Dave Kelsey | davidkel | NorfolkAndChance | **Retired maintainers** | Name | GitHub | Chat | |---------------------------|------------------|----------------| -| FeihuJiang | feihujiang | FlyingTiger | -| HaojunZhou | haojun | haojun | +| FeihuJiang | feihujiang | | +| HaojunZhou | haojun | | Contributors @@ -25,10 +25,9 @@ Contributors | Name | GitHub | Chat | |---------------------------|------------------|----------------| -| Benjamin Burns | benjamincburns | benjamincburns | +| Benjamin Burns | benjamincburns | | | Chenxi Li | vita-dounai | | -| Jason you | Jasonyou1995 | Jasonyou | -| Lynn Muswere | Lynn14m | Lynn14m | +| Jason you | Jasonyou1995 | | Packages @@ -38,14 +37,14 @@ The following is a list of packages and codeowners with familiarity in the area | Component | Contact(s) | |---------------------------|------------------| -| Caliper cli | klenik, nkl199, davidkel | -| Caliper core | klenik, nkl199, davidkel | -| Caliper publish | klenik, nkl199, davidkel | -| Caliper ethereum | benjamincburns, shemnon | -| Caliper fabric | klenik, nkl199, davidkel | -| Caliper fisco bcos | vita-dounai | -| Caliper gui dashboard | Jasonyou | -| Caliper gui server | Jasonyou | -| Caliper generator | Lynn14m, nkl199 | +| Caliper cli | A Klenik, N Lincoln, D Kelsey | +| Caliper core | A Klenik, N Lincoln, D Kelsey | +| Caliper publish | A Klenik, N Lincoln, D Kelsey | +| Caliper ethereum | Benjamin Burns | +| Caliper fabric | A Klenik, N Lincoln, D Kelsey | +| Caliper fisco bcos | Chenxi Li | +| Caliper gui dashboard | Jason you | +| Caliper gui server | Jason you | +| Caliper generator | N Lincoln, D Kelsey | Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License. diff --git a/PULL_REQUEST_TEMPLATE.md b/PULL_REQUEST_TEMPLATE.md index 4c1ae4786..6c2305a35 100644 --- a/PULL_REQUEST_TEMPLATE.md +++ b/PULL_REQUEST_TEMPLATE.md @@ -25,7 +25,7 @@ - [ ] [Stack Overflow issues](http://stackoverflow.com/tags/hyperledger-caliper) - [ ] [GitHub Issues](https://github.com/hyperledger/caliper/issues) -- [ ] [Rocket Chat history](https://chat.hyperledger.org/channel/caliper) +- [ ] [Discord history](https://discord.com/channels/905194001349627914/941417677778473031) diff --git a/README.md b/README.md index f59cbc129..e58cccb23 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ [![npm (scoped)](https://img.shields.io/npm/v/@hyperledger/caliper-cli?label=version)](https://www.npmjs.com/package/@hyperledger/caliper-cli) [![npm](https://img.shields.io/npm/dt/@hyperledger/caliper-cli?label=npm%20downloads)](https://www.npmjs.com/package/@hyperledger/caliper-cli) [![Docker Pulls](https://img.shields.io/docker/pulls/hyperledger/caliper)](https://hub.docker.com/r/hyperledger/caliper) -[![Rocket.Chat](https://img.shields.io/badge/rocket.chat-caliper-red)](https://chat.hyperledger.org/channel/caliper) +[![Discord.Chat](https://img.shields.io/badge/discord-caliper-red)](https://discord.com/channels/905194001349627914/941417677778473031) [![Mailing list](https://img.shields.io/badge/mailing%20list-caliper-blue)](https://lists.hyperledger.org/g/caliper/topics) Welcome to the Hyperledger Caliper project. Caliper is a blockchain performance benchmark framework, which allows users to test different blockchain solutions with predefined use cases, and get a set of performance test results. @@ -36,12 +36,10 @@ See the [related documentation page](https://hyperledger.github.io/caliper/). ## How to contact us If you have any issues using Caliper that the documentation does not help you solve, please reach out to us through the following methods: -* [RocketChat](https://chat.hyperledger.org/channel/caliper) Please feel free to contact us on Rocket Chat (instant messaging). We monitor that channel as close as possible, but even if you don't have a problem that needs resolving, why not jump on and say hi ... we'd love to hear from you about your experiences and any new features you think we should work on. +* [Discord](https://discord.com/channels/905194001349627914/941417677778473031) Please feel free to contact us on Discord (instant messaging). We monitor the Caliper channels as closely as possible, but even if you don't have a problem that needs resolving, why not jump on and say hi ... we'd love to hear from you about your experiences and any new features you think we should work on. * [Issues](https://github.com/hyperledger/caliper/issues) Feel free to raise an issue if you are facing a Caliper related problem -Caliper interacts with multiple blockchain technologies and consequently it *might* be an issue with the underlying blockchain technology being interacted with. You can seek specific help on these technologies within the following Rocket Chat channels: -* [Hyperledger Besu](https://chat.hyperledger.org/channel/besu) -* [Hyperledger Fabric](https://chat.hyperledger.org/channel/fabric) +Caliper interacts with multiple blockchain technologies and consequently it *might* be an issue with the underlying blockchain technology being interacted with. You can seek specific help on these technologies on the same Discord server such as the Fabric or Besu channels. ## How to contribute