[camel] branch main updated: (chores) doc: unify the contributing documentation

[or...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

orpiske pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/main by this push:
     new 316650573ab (chores) doc: unify the contributing documentation
316650573ab is described below

commit 316650573aba338c86c4b78a09c7765ea9830b36
Author: Otavio Rodolfo Piske <an...@gmail.com>
AuthorDate: Thu Jun 29 16:14:11 2023 +0200

    (chores) doc: unify the contributing documentation
---
 CONTRIBUTING.md | 29 +----------------------------
 1 file changed, 1 insertion(+), 28 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index e0353495494..f9e04ab75e3 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,30 +1,3 @@
 ## Contributing to Apache Camel
-First of all, thank you for having an interest in contributing to Apache Camel.
-If this is your first contribution to Camel, please review [the guidelines for contributing to Camel and its related projects](https://camel.apache.org/community/contributing/).
-
-Then follow these simple guidelines for working on the code and committing your changes.
-
-- Fork and then clone the GitHub camel repository:
-
-    git clone https://github.com/your-github-username/camel.git
-
-- Build the project using Maven. For Camel versions 3.x and older:
-
-    mvn clean install -Pfastinstall 
-
-- Build the project using Maven. For Camel versions 4.x and newer (on the `main` branch):
-
-    mvn clean install -Dquickly
-
-- Add a unit test with assertions for your changes.
-
-- Run Checkstyle using the `sourcecheck` profile in Maven:
-
-    mvn clean install -Psourcecheck
-
-- Check the documentation (.adoc file) for the code which you have modified and update it if required. For example if you have added or modified a component, the documentation file is in the src/main/docs folder.
-
-- Write a commit message which references the related JIRA or GitHub issue and includes some detail of your changes.
-- Push to your fork and create a pull request.
-- Stay engaged, follow and respond to comments or questions you might be asked by the Camel team.
 
+Please look at the [contributing guide](./docs/main/modules/contributing/pages/index.adoc).