[Docs] keep only one full table of maintainers in CONTRIBUTING.md

CONTRIBUTING.md

@@ -15,18 +15,7 @@ Before sending your pull requests, ensure that you follow this checklist:
 
 * Ensure that [unit tests](CONTRIBUTING.md#unit-tests) pass. Include logs from tests as attachments to the pull request.
 
-* Ensure that corresponding maintainer GitHub team is assigned to the PR review.
-
-  | GitHub team name | Description |
-  :-----------|:------------|
-  | @oneapi-src/onemkl-maintain  | All oneMKL maintainers |
-  | @oneapi-src/onemkl-arch-write | oneMKL Architecture maintainers |
-  | @oneapi-src/onemkl-blas-write | oneMKL BLAS maintainers |
-  | @oneapi-src/onemkl-dft-write | oneMKL DFT maintainers |
-  | @oneapi-src/onemkl-lapack-write | oneMKL LAPACK maintainers |
-  | @oneapi-src/onemkl-rng-write | oneMKL RNG maintainers |
-  | @oneapi-src/onemkl-sparse-write | oneMKL Sparse Algebra maintainers |
-  | @oneapi-src/onemkl-vm-write | oneMKL Vector Math maintainers |
+* Ensure that corresponding [maintainer GitHub team](#onemkl-interfaces-maintainers) is assigned to the PR review.
 
 ## Library Functionality Guidelines
 
@@ -58,6 +47,7 @@ Please also provide the following details as part of the RFC:
 
 * What existing libraries have implementations of this function and can be used under the oneMKL interface.
 
+* Ensure that corresponding [maintainer GitHub team](#onemkl-interfaces-maintainers) is assigned to the RFC review.
 
 ## Bug Reporting
 
@@ -68,6 +58,22 @@ If you find a bug or problem, please open a request under [Issues](https://githu
 
 Report security issues to [email protected].
 
+## oneMKL Interfaces Maintainers
+
+For GitHub questions, issues, RFCs, or PRs you can contact maintainers via one of the following GitHub teams based on the topic:
+
+| GitHub team name | Description |
+:-----------|:------------|
+| @oneapi-src/onemkl-maintain  | All oneMKL Interfaces maintainers |
+| @oneapi-src/onemkl-arch-write | oneMKL Interfaces Architecture maintainers |
+| @oneapi-src/onemkl-blas-write | oneMKL Interfaces BLAS maintainers |
+| @oneapi-src/onemkl-dft-write | oneMKL Interfaces DFT maintainers |
+| @oneapi-src/onemkl-lapack-write | oneMKL Interfaces LAPACK maintainers |
+| @oneapi-src/onemkl-rng-write | oneMKL Interfaces RNG maintainers |
+| @oneapi-src/onemkl-sparse-write | oneMKL Interfaces Sparse Algebra maintainers |
+| @oneapi-src/onemkl-vm-write | oneMKL Interfaces Vector Math maintainers |
+
+Please read [MAINTAINERS page](MAINTAINERS.md) for more information about maintainer roles, responsibilities, and how to become one of them.
 
 ## Coding Style
 

MAINTAINERS.md

@@ -72,12 +72,12 @@ The process of becoming a Domain maintainer is:
 
 | GitHub team name | Domain maintainers |
 :-----------|:------------|
-| @oneapi-src/onemkl-blas-write | oneMKL BLAS maintainers |
-| @oneapi-src/onemkl-dft-write | oneMKL DFT maintainers |
-| @oneapi-src/onemkl-lapack-write) | oneMKL LAPACK maintainers |
-| @oneapi-src/onemkl-rng-write | oneMKL RNG maintainers |
-| @oneapi-src/onemkl-sparse-write | oneMKL Sparse Algebra maintainers |
-| @oneapi-src/onemkl-vm-write | oneMKL Vector Math maintainers |
+| @oneapi-src/onemkl-blas-write | oneMKL Interfaces BLAS maintainers |
+| @oneapi-src/onemkl-dft-write | oneMKL Interfaces DFT maintainers |
+| @oneapi-src/onemkl-lapack-write) | oneMKL Interfaces LAPACK maintainers |
+| @oneapi-src/onemkl-rng-write | oneMKL Interfaces RNG maintainers |
+| @oneapi-src/onemkl-sparse-write | oneMKL Interfaces Sparse Algebra maintainers |
+| @oneapi-src/onemkl-vm-write | oneMKL Interfaces Vector Math maintainers |
 
 ## Architecture Maintainer
 Architecture maintainers are the most established contributors who are responsible for the
@@ -107,7 +107,7 @@ Privileges:
   * Can recommend Contributor or Domain maintainer to become Architecture maintainers.
 
 Process of becoming a maintainer:
-1. A Contributor or Domain maintainer requests to join oneMKL Architecture maintainers GitHub team
+1. A Contributor or Domain maintainer requests to join oneMKL Interfaces Architecture maintainers GitHub team
 (@oneapi-src/onemkl-arch-write).
 2. At least one of Architecture maintainers approves the request.
 

README.md

@@ -546,21 +546,6 @@ You can also join the mailing lists for the [UXL Foundation](https://lists.uxlfo
 
 You can contribute to this project and also contribute to [the specification for this project](https://oneapi-spec.uxlfoundation.org/specifications/oneapi/latest/elements/onemkl/source/). Please read the [CONTRIBUTING](CONTRIBUTING.md) page for more information. You can also contact oneMKL developers and maintainers via [UXL Foundation Slack](https://slack-invite.uxlfoundation.org/) using [#onemkl](https://uxlfoundation.slack.com/archives/onemkl) channel.
 
-For GitHub questions, issues, RFCs, or PRs you can contact maintainers via one of the following GitHub teams based on the topic:
-
-| GitHub team name | Description |
-:-----------|:------------|
-| @oneapi-src/onemkl-maintain  | All oneMKL maintainers |
-| @oneapi-src/onemkl-arch-write | oneMKL Architecture maintainers |
-| @oneapi-src/onemkl-blas-write | oneMKL BLAS maintainers |
-| @oneapi-src/onemkl-dft-write | oneMKL DFT maintainers |
-| @oneapi-src/onemkl-lapack-write | oneMKL LAPACK maintainers |
-| @oneapi-src/onemkl-rng-write | oneMKL RNG maintainers |
-| @oneapi-src/onemkl-sparse-write | oneMKL Sparse Algebra maintainers |
-| @oneapi-src/onemkl-vm-write | oneMKL Vector Math maintainers |
-
-Please read [MAINTAINERS page](MAINTAINERS.md) for more information about maintainer roles, responsibilities, and how to become one of them.
-
 ---
 
 ## License