docs: Update documentation for the migration to GitHub

Partially-resolves: COMPMID-8450
Signed-off-by: Andreas Flöjt <[email protected]>
Change-Id: I963c046e0a277ac2d7551e5146a21f0732f6f432

Author: andflo-Arm

CONTRIBUTING.md

@@ -1,11 +1 @@
-Please read https://artificial-intelligence.sites.arm.com/computelibrary/latest/contribution_guidelines.xhtml
-
-Here on github we only publish a snapshot of the main development branch for each release, that's the reason why we don't accept pull requests.
-
-Please submit your patch for review to review.mlplatform.org.
-
-The development is structured in the following way:
-
-    Release repository: https://github.com/arm-software/ComputeLibrary
-    Development repository: https://review.mlplatform.org/#/admin/projects/ml/ComputeLibrary
-    Please report issues here: https://github.com/ARM-software/ComputeLibrary/issues
+Please read https://artificial-intelligence.sites.arm.com/computelibrary/latest/contribution_guidelines.xhtml.

README.md

@@ -31,15 +31,6 @@ Key Features:
 - Advanced optimization techniques such as kernel fusion, Fast math enablement and texture utilization
 - Device and workload specific tuning using OpenCL tuner and GeMM optimized heuristics
 
-<br>
-
-| Repository  | Link                                                             |
-| ----------- | ---------------------------------------------------------------- |
-| Release     | https://github.com/arm-software/ComputeLibrary                   |
-| Development | https://review.mlplatform.org/#/admin/projects/ml/ComputeLibrary |
-
-<br>
-
 ## Documentation
 [![Documentation](https://img.shields.io/badge/documentation-latest-green)](https://artificial-intelligence.sites.arm.com/computelibrary/latest/index.xhtml)
 

REUSE.toml

@@ -48,7 +48,7 @@ SPDX-License-Identifier = "MIT"
 
 [[annotations]]
 path = ["CONTRIBUTING.md"]
-SPDX-FileCopyrightText = "2022-2024 Arm Limited"
+SPDX-FileCopyrightText = "2022-2025 Arm Limited"
 SPDX-License-Identifier = "MIT"
 
 [[annotations]]

docs/contributor_guide/contribution_guidelines.dox

@@ -1,5 +1,5 @@
 ///
-/// Copyright (c) 2019-2023 Arm Limited.
+/// Copyright (c) 2019-2023, 2025 Arm Limited.
 ///
 /// SPDX-License-Identifier: MIT
 ///
@@ -30,10 +30,7 @@ namespace arm_compute
 
 If you want to contribute to Arm Compute Library, be sure to review the following guidelines.
 
-The development is structured in the following way:
-- Release repository: https://github.com/arm-software/ComputeLibrary
-- Development repository: https://review.mlplatform.org/#/admin/projects/ml/ComputeLibrary
-- Please report issues here: https://github.com/ARM-software/ComputeLibrary/issues
+Contributions are accepted at <a href="https://github.com/arm-software/ComputeLibrary">arm-software/ComputeLibrary</a>.
 
 @section S5_0_inc_lang Inclusive language guideline
 As part of the initiative to use inclusive language, there are certain phrases and words that were removed or replaced by more inclusive ones. Examples include but not limited to:
@@ -481,22 +478,9 @@ void DoNewThing();
 
 @section S5_2_how_to_submit_a_patch How to submit a patch
 
-To be able to submit a patch to our development repository you need to have a GitHub account. With that, you will be able to sign in to Gerrit where your patch will be reviewed.
-
-Next step is to clone the Compute Library repository:
-
-	git clone "ssh://<your-github-id>@review.mlplatform.org:29418/ml/ComputeLibrary"
-
-If you have cloned from GitHub or through HTTP, make sure you add a new git remote using SSH:
-
-	git remote add acl-gerrit "ssh://<your-github-id>@review.mlplatform.org:29418/ml/ComputeLibrary"
-
-After that, you will need to upload an SSH key to https://review.mlplatform.org/#/settings/ssh-keys
-
-Then, make sure to install the commit-msg Git hook in order to add a change-ID to the commit message of your patch:
-
-	cd "ComputeLibrary" && mkdir -p .git/hooks && curl -Lo `git rev-parse --git-dir`/hooks/commit-msg https://review.mlplatform.org/tools/hooks/commit-msg; chmod +x `git rev-parse --git-dir`/hooks/commit-msg)
+To be able to submit a patch to our development repository you need to raise a pull request on GitHub.
 
+Keep your patch in a single commit, with a message that adheres to <a href="https://www.conventionalcommits.org/en/v1.0.0/">Conventional Commits</a>.
 When your patch is ready, remember to sign off your contribution by adding a line with your name and e-mail address to every git commit message:
 
 	Signed-off-by: John Doe <[email protected]>
@@ -507,22 +491,19 @@ You can add this to your patch with:
 
 	git commit -s --amend
 
-You are now ready to submit your patch for review:
-
-	git push acl-gerrit HEAD:refs/for/main
+You are now ready to submit your patch for review in a pull request.
 
 @section S5_3_code_review Patch acceptance and code review
 
-Once a patch is uploaded for review, there is a pre-commit test that runs on a Jenkins server for continuous integration tests. In order to be merged a patch needs to:
+Once a patch is uploaded for review, there is a pre-commit test that runs on a Jenkins server for continuous integration tests.
+In order to be merged, a patch needs to:
 
-- get a "+1 Verified" from the pre-commit job
-- get a "+1 Comments-Addressed", in case of comments from reviewers the committer has to address them all. A comment is considered addressed when the first line of the reply contains the word "Done"
-- get a "+2" from a reviewer, that means the patch has the final approval
+- pass the pre-commit job,
+- be squashed,
+- be approved by a Compute Library maintainer.
 
 At the moment, the Jenkins server is not publicly accessible and for security reasons patches submitted by non-allowlisted committers do not trigger the pre-commit tests. For this reason, one of the maintainers has to manually trigger the job.
 
-If the pre-commit test fails, the Jenkins job will post a comment on Gerrit with the details about the failure so that the committer will be able to reproduce the error and fix the issue, if any (sometimes there can be infrastructure issues, a test platform disconnecting for example, where the job needs to be retriggered).
-
 @section S5_4_patch_reversion Patch reversion policy
 
 If the contributed patch breaks our regression suite, we either