root
/
rabbitmq-server
mirror of https://github.com/rabbitmq/rabbitmq-server.git
1
0
Fork 0
Code Issues Actions 6 Packages Projects Releases Wiki Activity

Update CLA URL

This commit is contained in:
Michal Kuratczyk 2021-09-23 14:29:36 +02:00
parent 9b53e9fe43
commit 1a2126676d
19 changed files with 38 additions and 38 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CONTRIBUTING.md
View File

@ -12,7 +12,7 @@ The process is fairly standard:
* Create a branch with a descriptive name in the relevant repositories * Create a branch with a descriptive name in the relevant repositories
* Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
* Submit pull requests with an explanation what has been changed and **why** * Submit pull requests with an explanation what has been changed and **why**
* Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below) * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
* Be patient. We will get to your pull request eventually * Be patient. We will get to your pull request eventually
If what you are going to work on is a substantial change, please first ask the core team If what you are going to work on is a substantial change, please first ask the core team
@ -50,7 +50,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
## Contributor Agreement ## Contributor Agreement
If you want to contribute a non-trivial change, please submit a signed copy of our If you want to contribute a non-trivial change, please submit a signed copy of our
[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time [Contributor Agreement](https://cla.pivotal.io/) around the time
you submit your pull request. This will make it much easier (in some cases, possible) you submit your pull request. This will make it much easier (in some cases, possible)
for the RabbitMQ team at Pivotal to merge your contribution. for the RabbitMQ team at Pivotal to merge your contribution.

4
deps/amqp10_common/CONTRIBUTING.md vendored
View File

@ -13,7 +13,7 @@ The process is fairly standard:
* Create a branch with a descriptive name in the relevant repositories * Create a branch with a descriptive name in the relevant repositories
* Make your changes, run tests, commit with a [descriptive message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork * Make your changes, run tests, commit with a [descriptive message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
* Submit pull requests with an explanation what has been changed and **why** * Submit pull requests with an explanation what has been changed and **why**
* Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below) * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
* Be patient. We will get to your pull request eventually * Be patient. We will get to your pull request eventually
If what you are going to work on is a substantial change, please first ask the core team If what you are going to work on is a substantial change, please first ask the core team
@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
## Contributor Agreement ## Contributor Agreement
If you want to contribute a non-trivial change, please submit a signed copy of our If you want to contribute a non-trivial change, please submit a signed copy of our
[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time [Contributor Agreement](https://cla.pivotal.io/) around the time
you submit your pull request. This will make it much easier (in some cases, possible) you submit your pull request. This will make it much easier (in some cases, possible)
for the RabbitMQ team at Pivotal to merge your contribution. for the RabbitMQ team at Pivotal to merge your contribution.

4
deps/amqp_client/CONTRIBUTING.md vendored
View File

@ -13,7 +13,7 @@ The process is fairly standard:
* Create a branch with a descriptive name in the relevant repositories * Create a branch with a descriptive name in the relevant repositories
* Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
* Submit pull requests with an explanation what has been changed and **why** * Submit pull requests with an explanation what has been changed and **why**
* Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below) * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
* Be patient. We will get to your pull request eventually * Be patient. We will get to your pull request eventually
If what you are going to work on is a substantial change, please first ask the core team If what you are going to work on is a substantial change, please first ask the core team
@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
## Contributor Agreement ## Contributor Agreement
If you want to contribute a non-trivial change, please submit a signed copy of our If you want to contribute a non-trivial change, please submit a signed copy of our
[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time [Contributor Agreement](https://cla.pivotal.io/) around the time
you submit your pull request. This will make it much easier (in some cases, possible) you submit your pull request. This will make it much easier (in some cases, possible)
for the RabbitMQ team at Pivotal to merge your contribution. for the RabbitMQ team at Pivotal to merge your contribution.

4
deps/rabbit_common/CONTRIBUTING.md vendored
View File

@ -13,7 +13,7 @@ The process is fairly standard:
* Create a branch with a descriptive name in the relevant repositories * Create a branch with a descriptive name in the relevant repositories
* Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
* Submit pull requests with an explanation what has been changed and **why** * Submit pull requests with an explanation what has been changed and **why**
* Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below) * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
* Be patient. We will get to your pull request eventually * Be patient. We will get to your pull request eventually
If what you are going to work on is a substantial change, please first ask the core team If what you are going to work on is a substantial change, please first ask the core team
@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
## Contributor Agreement ## Contributor Agreement
If you want to contribute a non-trivial change, please submit a signed copy of our If you want to contribute a non-trivial change, please submit a signed copy of our
[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time [Contributor Agreement](https://cla.pivotal.io/) around the time
you submit your pull request. This will make it much easier (in some cases, possible) you submit your pull request. This will make it much easier (in some cases, possible)
for the RabbitMQ team at Pivotal to merge your contribution. for the RabbitMQ team at Pivotal to merge your contribution.

4
deps/rabbitmq_amqp1_0/CONTRIBUTING.md vendored
View File

@ -13,7 +13,7 @@ The process is fairly standard:
* Create a branch with a descriptive name in the relevant repositories * Create a branch with a descriptive name in the relevant repositories
* Make your changes, run tests, commit with a [descriptive message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork * Make your changes, run tests, commit with a [descriptive message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
* Submit pull requests with an explanation what has been changed and **why** * Submit pull requests with an explanation what has been changed and **why**
* Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below) * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
* Be patient. We will get to your pull request eventually * Be patient. We will get to your pull request eventually
If what you are going to work on is a substantial change, please first ask the core team If what you are going to work on is a substantial change, please first ask the core team
@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
## Contributor Agreement ## Contributor Agreement
If you want to contribute a non-trivial change, please submit a signed copy of our If you want to contribute a non-trivial change, please submit a signed copy of our
[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time [Contributor Agreement](https://cla.pivotal.io/) around the time
you submit your pull request. This will make it much easier (in some cases, possible) you submit your pull request. This will make it much easier (in some cases, possible)
for the RabbitMQ team at Pivotal to merge your contribution. for the RabbitMQ team at Pivotal to merge your contribution.

4
deps/rabbitmq_codegen/CONTRIBUTING.md vendored
View File

@ -13,7 +13,7 @@ The process is fairly standard:
* Create a branch with a descriptive name in the relevant repositories * Create a branch with a descriptive name in the relevant repositories
* Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
* Submit pull requests with an explanation what has been changed and **why** * Submit pull requests with an explanation what has been changed and **why**
* Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below) * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
* Be patient. We will get to your pull request eventually * Be patient. We will get to your pull request eventually
If what you are going to work on is a substantial change, please first ask the core team If what you are going to work on is a substantial change, please first ask the core team
@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
## Contributor Agreement ## Contributor Agreement
If you want to contribute a non-trivial change, please submit a signed copy of our If you want to contribute a non-trivial change, please submit a signed copy of our
[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time [Contributor Agreement](https://cla.pivotal.io/) around the time
you submit your pull request. This will make it much easier (in some cases, possible) you submit your pull request. This will make it much easier (in some cases, possible)
for the RabbitMQ team at Pivotal to merge your contribution. for the RabbitMQ team at Pivotal to merge your contribution.

4
deps/rabbitmq_jms_topic_exchange/CONTRIBUTING.md vendored
View File

@ -13,7 +13,7 @@ The process is fairly standard:
* Create a branch with a descriptive name in the relevant repositories * Create a branch with a descriptive name in the relevant repositories
* Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
* Submit pull requests with an explanation what has been changed and **why** * Submit pull requests with an explanation what has been changed and **why**
* Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below) * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
* Be patient. We will get to your pull request eventually * Be patient. We will get to your pull request eventually
If what you are going to work on is a substantial change, please first ask the core team If what you are going to work on is a substantial change, please first ask the core team
@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
## Contributor Agreement ## Contributor Agreement
If you want to contribute a non-trivial change, please submit a signed copy of our If you want to contribute a non-trivial change, please submit a signed copy of our
[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time [Contributor Agreement](https://cla.pivotal.io/) around the time
you submit your pull request. This will make it much easier (in some cases, possible) you submit your pull request. This will make it much easier (in some cases, possible)
for the RabbitMQ team at Pivotal to merge your contribution. for the RabbitMQ team at Pivotal to merge your contribution.

4
deps/rabbitmq_management_agent/CONTRIBUTING.md vendored
View File

@ -13,7 +13,7 @@ The process is fairly standard:
* Create a branch with a descriptive name in the relevant repositories * Create a branch with a descriptive name in the relevant repositories
* Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
* Submit pull requests with an explanation what has been changed and **why** * Submit pull requests with an explanation what has been changed and **why**
* Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below) * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
* Be patient. We will get to your pull request eventually * Be patient. We will get to your pull request eventually
If what you are going to work on is a substantial change, please first ask the core team If what you are going to work on is a substantial change, please first ask the core team
@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
## Contributor Agreement ## Contributor Agreement
If you want to contribute a non-trivial change, please submit a signed copy of our If you want to contribute a non-trivial change, please submit a signed copy of our
[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time [Contributor Agreement](https://cla.pivotal.io/) around the time
you submit your pull request. This will make it much easier (in some cases, possible) you submit your pull request. This will make it much easier (in some cases, possible)
for the RabbitMQ team at Pivotal to merge your contribution. for the RabbitMQ team at Pivotal to merge your contribution.

4
deps/rabbitmq_random_exchange/CONTRIBUTING.md vendored
View File

@ -13,7 +13,7 @@ The process is fairly standard:
* Create a branch with a descriptive name in the relevant repositories * Create a branch with a descriptive name in the relevant repositories
* Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
* Submit pull requests with an explanation what has been changed and **why** * Submit pull requests with an explanation what has been changed and **why**
* Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below) * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
* Be patient. We will get to your pull request eventually * Be patient. We will get to your pull request eventually
If what you are going to work on is a substantial change, please first ask the core team If what you are going to work on is a substantial change, please first ask the core team
@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
## Contributor Agreement ## Contributor Agreement
If you want to contribute a non-trivial change, please submit a signed copy of our If you want to contribute a non-trivial change, please submit a signed copy of our
[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time [Contributor Agreement](https://cla.pivotal.io/) around the time
you submit your pull request. This will make it much easier (in some cases, possible) you submit your pull request. This will make it much easier (in some cases, possible)
for the RabbitMQ team at Pivotal to merge your contribution. for the RabbitMQ team at Pivotal to merge your contribution.

4
deps/rabbitmq_recent_history_exchange/CONTRIBUTING.md vendored
View File

@ -13,7 +13,7 @@ The process is fairly standard:
* Create a branch with a descriptive name in the relevant repositories * Create a branch with a descriptive name in the relevant repositories
* Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
* Submit pull requests with an explanation what has been changed and **why** * Submit pull requests with an explanation what has been changed and **why**
* Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below) * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
* Be patient. We will get to your pull request eventually * Be patient. We will get to your pull request eventually
If what you are going to work on is a substantial change, please first ask the core team If what you are going to work on is a substantial change, please first ask the core team
@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
## Contributor Agreement ## Contributor Agreement
If you want to contribute a non-trivial change, please submit a signed copy of our If you want to contribute a non-trivial change, please submit a signed copy of our
[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time [Contributor Agreement](https://cla.pivotal.io/) around the time
you submit your pull request. This will make it much easier (in some cases, possible) you submit your pull request. This will make it much easier (in some cases, possible)
for the RabbitMQ team at Pivotal to merge your contribution. for the RabbitMQ team at Pivotal to merge your contribution.

4
deps/rabbitmq_sharding/CONTRIBUTING.md vendored
View File

@ -13,7 +13,7 @@ The process is fairly standard:
* Create a branch with a descriptive name in the relevant repositories * Create a branch with a descriptive name in the relevant repositories
* Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
* Submit pull requests with an explanation what has been changed and **why** * Submit pull requests with an explanation what has been changed and **why**
* Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below) * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
* Be patient. We will get to your pull request eventually * Be patient. We will get to your pull request eventually
If what you are going to work on is a substantial change, please first ask the core team If what you are going to work on is a substantial change, please first ask the core team
@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
## Contributor Agreement ## Contributor Agreement
If you want to contribute a non-trivial change, please submit a signed copy of our If you want to contribute a non-trivial change, please submit a signed copy of our
[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time [Contributor Agreement](https://cla.pivotal.io/) around the time
you submit your pull request. This will make it much easier (in some cases, possible) you submit your pull request. This will make it much easier (in some cases, possible)
for the RabbitMQ team at Pivotal to merge your contribution. for the RabbitMQ team at Pivotal to merge your contribution.

4
deps/rabbitmq_stream/CONTRIBUTING.md vendored
View File

@ -13,7 +13,7 @@ The process is fairly standard:
* Create a branch with a descriptive name in the relevant repositories * Create a branch with a descriptive name in the relevant repositories
* Make your changes, run tests, commit with a [descriptive message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork * Make your changes, run tests, commit with a [descriptive message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
* Submit pull requests with an explanation what has been changed and **why** * Submit pull requests with an explanation what has been changed and **why**
* Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below) * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
* Be patient. We will get to your pull request eventually * Be patient. We will get to your pull request eventually
If what you are going to work on is a substantial change, please first ask the core team If what you are going to work on is a substantial change, please first ask the core team
@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
## Contributor Agreement ## Contributor Agreement
If you want to contribute a non-trivial change, please submit a signed copy of our If you want to contribute a non-trivial change, please submit a signed copy of our
[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time [Contributor Agreement](https://cla.pivotal.io/) around the time
you submit your pull request. This will make it much easier (in some cases, possible) you submit your pull request. This will make it much easier (in some cases, possible)
for the RabbitMQ team at Pivotal to merge your contribution. for the RabbitMQ team at Pivotal to merge your contribution.

4
deps/rabbitmq_stream_common/CONTRIBUTING.md vendored
View File

@ -13,7 +13,7 @@ The process is fairly standard:
* Create a branch with a descriptive name in the relevant repositories * Create a branch with a descriptive name in the relevant repositories
* Make your changes, run tests, commit with a [descriptive message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork * Make your changes, run tests, commit with a [descriptive message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
* Submit pull requests with an explanation what has been changed and **why** * Submit pull requests with an explanation what has been changed and **why**
* Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below) * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
* Be patient. We will get to your pull request eventually * Be patient. We will get to your pull request eventually
If what you are going to work on is a substantial change, please first ask the core team If what you are going to work on is a substantial change, please first ask the core team
@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
## Contributor Agreement ## Contributor Agreement
If you want to contribute a non-trivial change, please submit a signed copy of our If you want to contribute a non-trivial change, please submit a signed copy of our
[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time [Contributor Agreement](https://cla.pivotal.io/) around the time
you submit your pull request. This will make it much easier (in some cases, possible) you submit your pull request. This will make it much easier (in some cases, possible)
for the RabbitMQ team at Pivotal to merge your contribution. for the RabbitMQ team at Pivotal to merge your contribution.

4
deps/rabbitmq_stream_management/CONTRIBUTING.md vendored
View File

@ -13,7 +13,7 @@ The process is fairly standard:
* Create a branch with a descriptive name in the relevant repositories * Create a branch with a descriptive name in the relevant repositories
* Make your changes, run tests, commit with a [descriptive message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork * Make your changes, run tests, commit with a [descriptive message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
* Submit pull requests with an explanation what has been changed and **why** * Submit pull requests with an explanation what has been changed and **why**
* Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below) * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
* Be patient. We will get to your pull request eventually * Be patient. We will get to your pull request eventually
If what you are going to work on is a substantial change, please first ask the core team If what you are going to work on is a substantial change, please first ask the core team
@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
## Contributor Agreement ## Contributor Agreement
If you want to contribute a non-trivial change, please submit a signed copy of our If you want to contribute a non-trivial change, please submit a signed copy of our
[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time [Contributor Agreement](https://cla.pivotal.io/) around the time
you submit your pull request. This will make it much easier (in some cases, possible) you submit your pull request. This will make it much easier (in some cases, possible)
for the RabbitMQ team at Pivotal to merge your contribution. for the RabbitMQ team at Pivotal to merge your contribution.

4
deps/rabbitmq_top/CONTRIBUTING.md vendored
View File

@ -13,7 +13,7 @@ The process is fairly standard:
* Create a branch with a descriptive name in the relevant repositories * Create a branch with a descriptive name in the relevant repositories
* Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
* Submit pull requests with an explanation what has been changed and **why** * Submit pull requests with an explanation what has been changed and **why**
* Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below) * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
* Be patient. We will get to your pull request eventually * Be patient. We will get to your pull request eventually
If what you are going to work on is a substantial change, please first ask the core team If what you are going to work on is a substantial change, please first ask the core team
@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
## Contributor Agreement ## Contributor Agreement
If you want to contribute a non-trivial change, please submit a signed copy of our If you want to contribute a non-trivial change, please submit a signed copy of our
[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time [Contributor Agreement](https://cla.pivotal.io/) around the time
you submit your pull request. This will make it much easier (in some cases, possible) you submit your pull request. This will make it much easier (in some cases, possible)
for the RabbitMQ team at Pivotal to merge your contribution. for the RabbitMQ team at Pivotal to merge your contribution.

4
deps/rabbitmq_trust_store/CONTRIBUTING.md vendored
View File

@ -13,7 +13,7 @@ The process is fairly standard:
* Create a branch with a descriptive name in the relevant repositories * Create a branch with a descriptive name in the relevant repositories
* Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
* Submit pull requests with an explanation what has been changed and **why** * Submit pull requests with an explanation what has been changed and **why**
* Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below) * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
* Be patient. We will get to your pull request eventually * Be patient. We will get to your pull request eventually
If what you are going to work on is a substantial change, please first ask the core team If what you are going to work on is a substantial change, please first ask the core team
@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
## Contributor Agreement ## Contributor Agreement
If you want to contribute a non-trivial change, please submit a signed copy of our If you want to contribute a non-trivial change, please submit a signed copy of our
[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time [Contributor Agreement](https://cla.pivotal.io/) around the time
you submit your pull request. This will make it much easier (in some cases, possible) you submit your pull request. This will make it much easier (in some cases, possible)
for the RabbitMQ team at Pivotal to merge your contribution. for the RabbitMQ team at Pivotal to merge your contribution.

4
deps/rabbitmq_web_dispatch/CONTRIBUTING.md vendored
View File

@ -13,7 +13,7 @@ The process is fairly standard:
* Create a branch with a descriptive name in the relevant repositories * Create a branch with a descriptive name in the relevant repositories
* Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
* Submit pull requests with an explanation what has been changed and **why** * Submit pull requests with an explanation what has been changed and **why**
* Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below) * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
* Be patient. We will get to your pull request eventually * Be patient. We will get to your pull request eventually
If what you are going to work on is a substantial change, please first ask the core team If what you are going to work on is a substantial change, please first ask the core team
@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
## Contributor Agreement ## Contributor Agreement
If you want to contribute a non-trivial change, please submit a signed copy of our If you want to contribute a non-trivial change, please submit a signed copy of our
[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time [Contributor Agreement](https://cla.pivotal.io/) around the time
you submit your pull request. This will make it much easier (in some cases, possible) you submit your pull request. This will make it much easier (in some cases, possible)
for the RabbitMQ team at Pivotal to merge your contribution. for the RabbitMQ team at Pivotal to merge your contribution.

4
deps/rabbitmq_web_mqtt_examples/CONTRIBUTING.md vendored
View File

@ -13,7 +13,7 @@ The process is fairly standard:
* Create a branch with a descriptive name in the relevant repositories * Create a branch with a descriptive name in the relevant repositories
* Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
* Submit pull requests with an explanation what has been changed and **why** * Submit pull requests with an explanation what has been changed and **why**
* Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below) * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
* Be patient. We will get to your pull request eventually * Be patient. We will get to your pull request eventually
If what you are going to work on is a substantial change, please first ask the core team If what you are going to work on is a substantial change, please first ask the core team
@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
## Contributor Agreement ## Contributor Agreement
If you want to contribute a non-trivial change, please submit a signed copy of our If you want to contribute a non-trivial change, please submit a signed copy of our
[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time [Contributor Agreement](https://cla.pivotal.io/) around the time
you submit your pull request. This will make it much easier (in some cases, possible) you submit your pull request. This will make it much easier (in some cases, possible)
for the RabbitMQ team at Pivotal to merge your contribution. for the RabbitMQ team at Pivotal to merge your contribution.

4
deps/rabbitmq_web_stomp/CONTRIBUTING.md vendored
View File

@ -13,7 +13,7 @@ The process is fairly standard:
* Create a branch with a descriptive name in the relevant repositories * Create a branch with a descriptive name in the relevant repositories
* Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork * Make your changes, run tests, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork
* Submit pull requests with an explanation what has been changed and **why** * Submit pull requests with an explanation what has been changed and **why**
* Submit a filled out and signed [Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) if needed (see below) * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below)
* Be patient. We will get to your pull request eventually * Be patient. We will get to your pull request eventually
If what you are going to work on is a substantial change, please first ask the core team If what you are going to work on is a substantial change, please first ask the core team
@ -28,7 +28,7 @@ See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
## Contributor Agreement ## Contributor Agreement
If you want to contribute a non-trivial change, please submit a signed copy of our If you want to contribute a non-trivial change, please submit a signed copy of our
[Contributor Agreement](https://github.com/rabbitmq/ca#how-to-submit) around the time [Contributor Agreement](https://cla.pivotal.io/) around the time
you submit your pull request. This will make it much easier (in some cases, possible) you submit your pull request. This will make it much easier (in some cases, possible)
for the RabbitMQ team at Pivotal to merge your contribution. for the RabbitMQ team at Pivotal to merge your contribution.