chore: replace oneapi-src with uxlfoundation

.ci/env/tbb.bat

@@ -18,7 +18,7 @@ rem ============================================================================
 rem req: PowerShell 3.0+
 powershell.exe -command "if ($PSVersionTable.PSVersion.Major -ge 3) {exit 1} else {Write-Host \"The script requires PowerShell 3.0 or above (current version: $($PSVersionTable.PSVersion.Major).$($PSVersionTable.PSVersion.Minor))\"}" && goto Error_load
 
-set TBBURLROOT=https://github.com/oneapi-src/oneTBB/releases/download/v2021.5.0/
+set TBBURLROOT=https://github.com/uxlfoundation/oneTBB/releases/download/v2021.5.0/
 set TBBVERSION=oneapi-tbb-2021.5.0
 set TBBPACKAGE=%TBBVERSION%-win
 
@@ -41,7 +41,7 @@ if not exist "%DST%\win\bin" (
 
     if not exist %DST%\win\tbb\redist\intel64\vc14 powershell.exe -command "New-Item -Path \"%DST%\win\tbb\redist\intel64\vc14\" -ItemType Directory"
 
-    goto Exit 
+    goto Exit
 
 :Error_load
     echo tbb.bat : Error: Failed to load %TBBURL% to %DST%, try to load it manually

.ci/env/tbb.sh

@@ -120,7 +120,7 @@ sudo apt-get install build-essential gcc gfortran cmake -y
 tbb_src=${tbb_src:-${ONEDAL_DIR}/__work/onetbb-src}
 if [[ ! -d "${tbb_src}" ]] ; then
   TBB_VERSION="${TBB_VERSION:-${TBB_DEFAULT_VERSION}}"
-  git clone --depth 1 --branch "${TBB_VERSION}" https://github.com/oneapi-src/oneTBB.git "${tbb_src}"
+  git clone --depth 1 --branch "${TBB_VERSION}" https://github.com/uxlfoundation/oneTBB.git "${tbb_src}"
 fi
 
 rm -rf "${tbb_prefix}"

.github/CODEOWNERS

@@ -18,8 +18,8 @@ WORKSPACE      @Alexsandruss @napetrov @homksei @ahuber21 @ethanglaser
 # Build & dev infrastructure
 make*          @Alexsandruss
 cmake/         @Alexsandruss
-deploy/        @Alexsandruss @napetrov @homksei @ahuber21 @ethanglaser 
-dev/           @Alexsandruss @napetrov @homksei @ahuber21 @ethanglaser 
+deploy/        @Alexsandruss @napetrov @homksei @ahuber21 @ethanglaser
+dev/           @Alexsandruss @napetrov @homksei @ahuber21 @ethanglaser
 
 # C++ code
 cpp/           @Alexsandruss @samir-nasibli @Alexandr-Solovev
@@ -28,8 +28,8 @@ cpp/           @Alexsandruss @samir-nasibli @Alexandr-Solovev
 dtrees         @razdoburdin @ahuber21 @avolkov-intel @icfaust
 
 # Governance and process
-/.github/CODEOWNERS @oneapi-src/oneDAL-maintainer
-/SECURITY.md @oneapi-src/oneDAL-maintainer
-/MAINTAINERS.md @oneapi-src/oneDAL-maintainer
-/CONTRIBUTING.md @oneapi-src/oneDAL-maintainer
-/CODE_OF_CONDUCT.md @oneapi-src/oneDAL-maintainer
+/.github/CODEOWNERS @uxlfoundation/oneDAL-maintain
+/SECURITY.md @uxlfoundation/oneDAL-maintain
+/MAINTAINERS.md @uxlfoundation/oneDAL-maintain
+/CONTRIBUTING.md @uxlfoundation/oneDAL-maintain
+/CODE_OF_CONDUCT.md @uxlfoundation/oneDAL-maintain

.github/workflows/docker-validation-nightly.yml

@@ -30,7 +30,7 @@ concurrency:
 jobs:
   validate:
     name: Docker validation
-    if: github.repository == 'oneapi-src/oneDAL'
+    if: github.repository == 'uxlfoundation/oneDAL'
     runs-on: ubuntu-latest
     steps:
       - name: Checkout

.github/workflows/label-enforcement.yml

@@ -19,7 +19,7 @@ jobs:
     steps:
       - name: test
         run: |
-          LABELS=`gh api -H "Accept: application/vnd.github+json" /repos/oneapi-src/oneDAL/issues/${{ github.event.pull_request.number }}/labels | jq '[.[].name]'`
+          LABELS=`gh api -H "Accept: application/vnd.github+json" /repos/uxlfoundation/oneDAL/issues/${{ github.event.pull_request.number }}/labels | jq '[.[].name]'`
           echo $LABELS
           if [[ $LABELS == "[]" ]] || [[ $LABELS == "[\"RFC\"]" ]]; then
             echo "::error::No label set on the pull request"

.github/workflows/openssf-scorecard.yml

@@ -16,7 +16,7 @@ permissions: read-all
 jobs:
   analysis:
     name: Scorecard analysis
-    if: github.repository == 'oneapi-src/oneDAL'
+    if: github.repository == 'uxlfoundation/oneDAL'
     runs-on: ubuntu-latest
     permissions:
       # Needed to upload the results to code-scanning dashboard.

CONTRIBUTING.md

@@ -18,22 +18,22 @@
 # How to Contribute
 We welcome community contributions to Intel(R) oneAPI Data Analytics Library. You can:
 
-- Submit your changes directly with a [pull request](https://github.com/oneapi-src/oneDAL/pulls).
-- Log a bug or make a feature request with an [issue](https://github.com/oneapi-src/oneDAL/issues).
+- Submit your changes directly with a [pull request](https://github.com/uxlfoundation/oneDAL/pulls).
+- Log a bug or make a feature request with an [issue](https://github.com/uxlfoundation/oneDAL/issues).
 
 Refer to our guidelines on [pull requests](#pull-requests) and [issues](#issues) before you proceed.
 
 ## Contacting maintainers
 You may reach out to Intel project maintainers privately at onedal.maintainers@intel.com.
-[Codeowners](https://github.com/oneapi-src/oneDAL/blob/main/.github/CODEOWNERS) configuration defines specific maintainers for corresponding code sections, however it's currently limited to Intel members. With further migration to UXL we will be changing this, but here are non-Intel contacts:
+[Codeowners](https://github.com/uxlfoundation/oneDAL/blob/main/.github/CODEOWNERS) configuration defines specific maintainers for corresponding code sections, however it's currently limited to Intel members. With further migration to UXL we will be changing this, but here are non-Intel contacts:
 
 For ARM specifics you may contact: [@rakshithgb-fujitsu](https://github.com/rakshithgb-fujitsu/)
 
 For RISC-V specifics you may contact: [@keeranroth](https://github.com/keeranroth/)
 
 ## Issues
 
-Use [GitHub issues](https://github.com/oneapi-src/oneDAL/issues) to:
+Use [GitHub issues](https://github.com/uxlfoundation/oneDAL/issues) to:
 - report an issue
 - make a feature request
 
@@ -43,11 +43,11 @@ Use [GitHub issues](https://github.com/oneapi-src/oneDAL/issues) to:
 
 To contribute your changes directly to the repository, do the following:
 - Make sure you can build the product and run all the examples with your patch.
-- Product uses bazel for validation and your changes should pass tests. Please add new tests as necessary. [Bazel Guide for oneDAL](https://github.com/oneapi-src/oneDAL/tree/main/dev/bazel)
+- Product uses bazel for validation and your changes should pass tests. Please add new tests as necessary. [Bazel Guide for oneDAL](https://github.com/uxlfoundation/oneDAL/tree/main/dev/bazel)
 - Make sure your code is in line with our [coding style](#code-style) as `clang-format` is one of the checks in our public CI.
 - For a larger feature, provide a relevant example, and tests.
 - [Document](#documentation-guidelines) your code.
-- [Submit](https://github.com/oneapi-src/oneDAL/pulls) a pull request into the `main` branch.
+- [Submit](https://github.com/uxlfoundation/oneDAL/pulls) a pull request into the `main` branch.
 
 Public and private CIs are enabled for the repository. Your PR should pass all of our checks. We will review your contribution and, if any additional fixes or modifications are necessary, we may give some feedback to guide you. When accepted, your pull request will be merged into our GitHub* repository.
 
@@ -57,7 +57,7 @@ Public and private CIs are enabled for the repository. Your PR should pass all o
 
 **Prerequisites:** ClangFormat `9.0.0` or later
 
-Our repository contains [clang-format configurations](https://github.com/oneapi-src/oneDAL/blob/main/.clang-format) that you should use on your code. To do this, run:
+Our repository contains [clang-format configurations](https://github.com/uxlfoundation/oneDAL/blob/main/.clang-format) that you should use on your code. To do this, run:
 
 ```
 clang-format style=file <your file>
@@ -67,7 +67,7 @@ Refer to [ClangFormat documentation](https://clang.llvm.org/docs/ClangFormat.htm
 
 ### editorconfig-checker
 
-We also recommend using [editorconfig-checker](https://github.com/editorconfig-checker/editorconfig-checker) to ensure your code adheres to the project's coding style. EditorConfig-Checker is a command-line tool that checks your code against the rules defined in the [.editorconfig](https://github.com/oneapi-src/oneDAL/blob/main/.editorconfig) file.
+We also recommend using [editorconfig-checker](https://github.com/editorconfig-checker/editorconfig-checker) to ensure your code adheres to the project's coding style. EditorConfig-Checker is a command-line tool that checks your code against the rules defined in the [.editorconfig](https://github.com/uxlfoundation/oneDAL/blob/main/.editorconfig) file.
 
 To use it, follow these steps:
 
@@ -81,23 +81,23 @@ editorconfig-checker
 
 ### Coding Guidelines
 
-For your convenience we also added [coding guidelines](http://oneapi-src.github.io/oneDAL/contribution/coding_guide.html) with examples and detailed descriptions of the coding style oneDAL follows. We encourage you to consult them when writing your code.
+For your convenience we also added [coding guidelines](http://uxlfoundation.github.io/oneDAL/contribution/coding_guide.html) with examples and detailed descriptions of the coding style oneDAL follows. We encourage you to consult them when writing your code.
 
 ## Custom Components
 
 ### CPU Features Dispatching
 
 oneDAL provides binaries that can contain code targeting different architectural extensions of a base instruction set architecture (ISA). For example, code paths can exist for Intel(R) SSE2, Intel(R) AVX2, Intel(R) AVX-512, etc. extensions, on top of the x86-64 base architecture.
 When run on a specific hardware implementation like Haswell, Skylake-X, etc., oneDAL chooses the code path which is most suitable for that implementation.
-Contributors should leverage [CPU Features Dispatching](http://oneapi-src.github.io/oneDAL/contribution/cpu_features.html) mechanism to implement the code of the algorithms that can perform most optimally on various hardware implementations.
+Contributors should leverage [CPU Features Dispatching](http://uxlfoundation.github.io/oneDAL/contribution/cpu_features.html) mechanism to implement the code of the algorithms that can perform most optimally on various hardware implementations.
 
 ### Threading Layer
 
-In the source code of the algorithms, oneDAL does not use threading primitives directly. All the threading primitives used within oneDAL form are called the [threading layer](http://oneapi-src.github.io/oneDAL/contribution/threading.html). Contributors should leverage the primitives from the layer to implement parallel algorithms.
+In the source code of the algorithms, oneDAL does not use threading primitives directly. All the threading primitives used within oneDAL form are called the [threading layer](http://uxlfoundation.github.io/oneDAL/contribution/threading.html). Contributors should leverage the primitives from the layer to implement parallel algorithms.
 
 ## Documentation Guidelines
 
-oneDAL uses `Doxygen` for inline comments in public header files that are used to build the API reference and  `reStructuredText` for the Developer Guide. See [oneDAL documentation](https://oneapi-src.github.io/oneDAL/) for reference.
+oneDAL uses `Doxygen` for inline comments in public header files that are used to build the API reference and  `reStructuredText` for the Developer Guide. See [oneDAL documentation](https://uxlfoundation.github.io/oneDAL/) for reference.
 
 ---
 **Note:** oneDAL is licensed under [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0). By contributing to the project, you agree to the license and copyright terms therein and release your contribution under these terms.

INSTALL.md

@@ -37,13 +37,13 @@ https://www.intel.com/content/www/us/en/developer/tools/oneapi/base-toolkit.html
 
 ## Docker Development Environment
 
-[Docker file](https://github.com/oneapi-src/oneDAL/tree/main/dev/docker) with the oneDAL development environment
+[Docker file](https://github.com/uxlfoundation/oneDAL/tree/main/dev/docker) with the oneDAL development environment
 is available as an alternative to the manual setup.
 
 ## Installation Steps
 1. Clone the sources from GitHub\* as follows:
 
-        git clone https://github.com/oneapi-src/oneDAL.git
+        git clone https://github.com/uxlfoundation/oneDAL.git
 
 2. Set the PATH environment variable to the MSYS2\* bin directory (Windows\* only). For example:
 
@@ -171,7 +171,7 @@ cd daal/latest
 source env/vars.sh
 ```
 
-The provided unit tests for the library can be executed through the Bazel system - see the [Bazel docs](https://github.com/oneapi-src/oneDAL/tree/main/dev/bazel) for more information.
+The provided unit tests for the library can be executed through the Bazel system - see the [Bazel docs](https://github.com/uxlfoundation/oneDAL/tree/main/dev/bazel) for more information.
 
 Examples of library usage will also be auto-generated as part of the build under path `daal/latest/examples/daal/cpp/source`. These can be built through CMake - assuming one starts from the release path `__release_{os_name}[_{compiler_name}]`, the following would do:
 

MAINTAINERS.md

@@ -51,7 +51,7 @@ Privileges:
 ## Code Owner
 
 A Code Owner has responsibility for a specific project component or a functional
-area. Code Owners are collectively responsible, with other Code Owners, 
+area. Code Owners are collectively responsible, with other Code Owners,
 for developing and maintaining their component or functional areas, including
 reviewing all changes to their their areas of responsibility and indicating
 whether those changes are ready to merge. They have a track record of
@@ -89,7 +89,7 @@ including name, Github username, and affiliation.
 
 
 ## Maintainer
-Maintainers are the most established contributors who are responsible for the 
+Maintainers are the most established contributors who are responsible for the
 project technical direction and participate in making decisions about the
 strategy and priorities of the project.
 
@@ -116,15 +116,15 @@ Privileges:
   * Can recommend Code Owners to become Maintainers.
 
 Process of becoming a maintainer:
-1. A Maintainer may nominate a current code owner to become a new Maintainer by 
+1. A Maintainer may nominate a current code owner to become a new Maintainer by
 opening a PR against MAINTAINERS.md file.
 2. A majority of the current Maintainers must then approve the PR.
 
 # Code Owners and Maintainers List
 
 ## oneDAL core
 
-Team: @oneapi-src/onedal-write
+Team: @uxlfoundation/onedal-write
 
 Currently entire Intel oneDAL team serves at contributor level and have corresponding rights
 with additional separation of roles coming with repository migration to UXL
@@ -135,7 +135,7 @@ with additional separation of roles coming with repository migration to UXL
 | ------------------ | --------------------- | ----------------- | ---------- |
 | Victoriya Fedotova | @Vika-F               | Intel Corporation | Maintainer |
 | Aleksandr Solovev  | @Alexandr-Solovev     | Intel Corporation | Maintainer |
-| Alexander Andreev  | @Alexsandruss         | Intel Corporation | Maintainer | 
+| Alexander Andreev  | @Alexsandruss         | Intel Corporation | Maintainer |
 
 ### AArch64