Replace files with symlinks

This prevents duplicated and out-of-date instructions.

2 files changed, 2 insertions, 172 deletions

diff --git a/deps/rabbitmq_peer_discovery_aws/CODE_OF_CONDUCT.md b/deps/rabbitmq_peer_discovery_aws/CODE_OF_CONDUCT.md
index 08697906fd..a3613c99f0 100644..120000
--- a/deps/rabbitmq_peer_discovery_aws/CODE_OF_CONDUCT.md
+++ b/deps/rabbitmq_peer_discovery_aws/CODE_OF_CONDUCT.md
@@ -1,44 +1 @@
-# Contributor Code of Conduct
-
-As contributors and maintainers of this project, and in the interest of fostering an open
-and welcoming community, we pledge to respect all people who contribute through reporting
-issues, posting feature requests, updating documentation, submitting pull requests or
-patches, and other activities.
-
-We are committed to making participation in this project a harassment-free experience for
-everyone, regardless of level of experience, gender, gender identity and expression,
-sexual orientation, disability, personal appearance, body size, race, ethnicity, age,
-religion, or nationality.
-
-Examples of unacceptable behavior by participants include:
-
- * The use of sexualized language or imagery
- * Personal attacks
- * Trolling or insulting/derogatory comments
- * Public or private harassment
- * Publishing other's private information, such as physical or electronic addresses,
-   without explicit permission
- * Other unethical or unprofessional conduct
-
-Project maintainers have the right and responsibility to remove, edit, or reject comments,
-commits, code, wiki edits, issues, and other contributions that are not aligned to this
-Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors
-that they deem inappropriate, threatening, offensive, or harmful.
-
-By adopting this Code of Conduct, project maintainers commit themselves to fairly and
-consistently applying these principles to every aspect of managing this project. Project
-maintainers who do not follow or enforce the Code of Conduct may be permanently removed
-from the project team.
-
-This Code of Conduct applies both within project spaces and in public spaces when an
-individual is representing the project or its community.
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by
-contacting a project maintainer at [info@rabbitmq.com](mailto:info@rabbitmq.com). All complaints will
-be reviewed and investigated and will result in a response that is deemed necessary and
-appropriate to the circumstances. Maintainers are obligated to maintain confidentiality
-with regard to the reporter of an incident.
-
-This Code of Conduct is adapted from the
-[Contributor Covenant](https://contributor-covenant.org), version 1.3.0, available at
-[contributor-covenant.org/version/1/3/0/](https://contributor-covenant.org/version/1/3/0/)
+../../CODE_OF_CONDUCT.md
\ No newline at end of file
diff --git a/deps/rabbitmq_peer_discovery_aws/CONTRIBUTING.md b/deps/rabbitmq_peer_discovery_aws/CONTRIBUTING.md
index 1fee78b7e8..f939e75f21 100644..120000
--- a/deps/rabbitmq_peer_discovery_aws/CONTRIBUTING.md
+++ b/deps/rabbitmq_peer_discovery_aws/CONTRIBUTING.md
@@ -1,128 +1 @@
-Thank you for using RabbitMQ and for taking the time to contribute to the project.
-This document has two main parts:
-
- * when and how to file GitHub issues for RabbitMQ projects
- * how to submit pull requests
-
-They intend to save you and RabbitMQ maintainers some time, so please
-take a moment to read through them.
-
-## Overview
-
-### GitHub issues
-
-The RabbitMQ team uses GitHub issues for _specific actionable items_ that
-engineers can work on. This assumes the following:
-
-* GitHub issues are not used for questions, investigations, root cause
-  analysis, discussions of potential issues, etc (as defined by this team)
-* Enough information is provided by the reporter for maintainers to work with
-
-The team receives many questions through various venues every single
-day. Frequently, these questions do not include the necessary details
-the team needs to begin useful work. GitHub issues can very quickly
-turn into a something impossible to navigate and make sense
-of. Because of this, questions, investigations, root cause analysis,
-and discussions of potential features are all considered to be
-[mailing list][rmq-users] material. If you are unsure where to begin,
-the [RabbitMQ users mailing list][rmq-users] is the right place.
-
-Getting all the details necessary to reproduce an issue, make a
-conclusion or even form a hypothesis about what's happening can take a
-fair amount of time. Please help others help you by providing a way to
-reproduce the behavior you're observing, or at least sharing as much
-relevant information as possible on the [RabbitMQ users mailing
-list][rmq-users].
-
-Please provide versions of the software used:
-
- * RabbitMQ server
- * Erlang
- * Operating system version (and distribution, if applicable)
- * All client libraries used
- * RabbitMQ plugins (if applicable)
-
-The following information greatly helps in investigating and reproducing issues:
-
- * RabbitMQ server logs
- * A code example or terminal transcript that can be used to reproduce
- * Full exception stack traces (a single line message is not enough!)
- * `rabbitmqctl report` and `rabbitmqctl environment` output
- * Other relevant details about the environment and workload, e.g. a traffic capture
- * Feel free to edit out hostnames and other potentially sensitive information.
-
-To make collecting much of this and other environment information, use
-the [`rabbitmq-collect-env`][rmq-collect-env] script. It will produce an archive with
-server logs, operating system logs, output of certain diagnostics commands and so on.
-Please note that **no effort is made to scrub any information that may be sensitive**.
-
-### Pull Requests
-
-RabbitMQ projects use pull requests to discuss, collaborate on and accept code contributions.
-Pull requests is the primary place of discussing code changes.
-
-Here's the recommended workflow:
-
- * [Fork the repository][github-fork] or repositories you plan on contributing to. If multiple
-   repositories are involved in addressing the same issue, please use the same branch name
-   in each repository
- * Create a branch with a descriptive name in the relevant repositories
- * Make your changes, run tests (usually with `make tests`), commit with a
-   [descriptive message][git-commit-msgs], push to your fork
- * Submit pull requests with an explanation what has been changed and **why**
- * Submit a filled out and signed [Contributor Agreement][ca-agreement] if needed (see below)
- * 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 for their opinion on the [RabbitMQ users mailing list][rmq-users].
-
-## Running Tests
-
-
-Integration tests of this plugin need AWS credentials and an SSH key pair.
-The credentials can be set in two ways:
-
- * Via a `$HOME/.aws/credentials` file
- * Using the `AWS_SECRET_ACCESS_KEY` and `AWS_ACCESS_KEY_ID`
-
-Below is an example of a `.aws/credentials` file:
-
-``` ini
-[default]
-aws_access_key_id = EXAMPLEACCESSKEYID
-aws_secret_access_key = a-secret-access-key
-```
-
-A private SSH key is also required to transfer a locally compiled version
-of the repository and transfer it to all remote nodes. It is set via the `SSH_KEY` environment
-variable.
-
-    make ct-integration
-
-will run integration tests [on AWS] only.
-
-    make tests
-
-will run all suites.
-
-## Code of Conduct
-
-See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
-
-## Contributor Agreement
-
-If you want to contribute a non-trivial change, please submit a signed
-copy of our [Contributor Agreement][ca-agreement] around the time 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.
-
-## Where to Ask Questions
-
-If something isn't clear, feel free to ask on our [mailing list][rmq-users].
-
-[rmq-collect-env]: https://github.com/rabbitmq/support-tools/blob/master/scripts/rabbitmq-collect-env
-[git-commit-msgs]: https://chris.beams.io/posts/git-commit/
-[rmq-users]: https://groups.google.com/forum/#!forum/rabbitmq-users
-[ca-agreement]: https://cla.pivotal.io/sign/rabbitmq
-[github-fork]: https://help.github.com/articles/fork-a-repo/
+../../CONTRIBUTING.md
\ No newline at end of file