From 82c103077c85ba2d67747214a827987b92ae2ceb Mon Sep 17 00:00:00 2001 From: Maria Kraynyuk Date: Mon, 21 Oct 2024 13:23:42 -0700 Subject: [PATCH 1/3] [README] clarify spec changes in ratification process --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 427c8f90e..1775bed1f 100644 --- a/README.md +++ b/README.md @@ -32,7 +32,7 @@ contributors as reviewers to the PR. 4. Organize offline review or/and bring the RFC to [UXL Foundation Math SIG forum](https://lists.uxlfoundation.org/g/Math-SIG), [UXL Foundation Open Source Working Group](https://lists.uxlfoundation.org/g/open-source-wg), or any other related forums in order to collect feedback. * It's recommended to keep all feedback as part of PR review, so it also will be documented in one place -5. If changes affect API defined by [oneMKL specification](https://oneapi-spec.uxlfoundation.org/specifications/oneapi/latest/elements/onemkl/source/) the design document must be reviewed by [UXL Foundation Math SIG forum](https://lists.uxlfoundation.org/g/Math-SIG) and contributed to [oneAPI specification](https://github.com/uxlfoundation/oneAPI-spec), and only after it the proposed changes can be implemented in this project. +5. If changes affect API defined by [oneMKL specification](https://oneapi-spec.uxlfoundation.org/specifications/oneapi/latest/elements/onemkl/source/) the related part of the design document must be converted to oneAPI specification RFC (as a new [issue](https://github.com/uxlfoundation/oneAPI-spec/issues) with \[RFC\] tag), reviewed by [UXL Foundation Math SIG forum](https://lists.uxlfoundation.org/g/Math-SIG), and contributed to [oneAPI specification](https://github.com/uxlfoundation/oneAPI-spec), and only after it the proposed changes can be implemented in this project. 6. Merge PR when it has all required approvals * It's recommended to add PR number to the commit message, so it will be easy to find the design discussion From 4c83a1397da62267ba9c66383071b7a4a24ca4f2 Mon Sep 17 00:00:00 2001 From: Maria Kraynyuk Date: Tue, 22 Oct 2024 15:14:04 -0700 Subject: [PATCH 2/3] Update README.md Co-authored-by: Romain Biessy --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1775bed1f..6a876e08d 100644 --- a/README.md +++ b/README.md @@ -32,7 +32,7 @@ contributors as reviewers to the PR. 4. Organize offline review or/and bring the RFC to [UXL Foundation Math SIG forum](https://lists.uxlfoundation.org/g/Math-SIG), [UXL Foundation Open Source Working Group](https://lists.uxlfoundation.org/g/open-source-wg), or any other related forums in order to collect feedback. * It's recommended to keep all feedback as part of PR review, so it also will be documented in one place -5. If changes affect API defined by [oneMKL specification](https://oneapi-spec.uxlfoundation.org/specifications/oneapi/latest/elements/onemkl/source/) the related part of the design document must be converted to oneAPI specification RFC (as a new [issue](https://github.com/uxlfoundation/oneAPI-spec/issues) with \[RFC\] tag), reviewed by [UXL Foundation Math SIG forum](https://lists.uxlfoundation.org/g/Math-SIG), and contributed to [oneAPI specification](https://github.com/uxlfoundation/oneAPI-spec), and only after it the proposed changes can be implemented in this project. +5. If the changes affect the API defined by [oneMKL specification](https://oneapi-spec.uxlfoundation.org/specifications/oneapi/latest/elements/onemkl/source/) a new [issue](https://github.com/uxlfoundation/oneAPI-spec/issues) with the \[RFC\] tag must be created to describe the API changes. The specification RFC must be reviewed by [UXL Foundation Math SIG forum](https://lists.uxlfoundation.org/g/Math-SIG), and only after it the proposed changes can be implemented in this project. 6. Merge PR when it has all required approvals * It's recommended to add PR number to the commit message, so it will be easy to find the design discussion From 654292875ed583055188ed7989d8c023e9ded9c3 Mon Sep 17 00:00:00 2001 From: Maria Kraynyuk Date: Wed, 23 Oct 2024 11:30:43 -0700 Subject: [PATCH 3/3] Update README.md Co-authored-by: Dai-Ni Hsieh --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6a876e08d..96126b8bd 100644 --- a/README.md +++ b/README.md @@ -32,7 +32,7 @@ contributors as reviewers to the PR. 4. Organize offline review or/and bring the RFC to [UXL Foundation Math SIG forum](https://lists.uxlfoundation.org/g/Math-SIG), [UXL Foundation Open Source Working Group](https://lists.uxlfoundation.org/g/open-source-wg), or any other related forums in order to collect feedback. * It's recommended to keep all feedback as part of PR review, so it also will be documented in one place -5. If the changes affect the API defined by [oneMKL specification](https://oneapi-spec.uxlfoundation.org/specifications/oneapi/latest/elements/onemkl/source/) a new [issue](https://github.com/uxlfoundation/oneAPI-spec/issues) with the \[RFC\] tag must be created to describe the API changes. The specification RFC must be reviewed by [UXL Foundation Math SIG forum](https://lists.uxlfoundation.org/g/Math-SIG), and only after it the proposed changes can be implemented in this project. +5. If the changes affect the API defined by [oneMKL specification](https://oneapi-spec.uxlfoundation.org/specifications/oneapi/latest/elements/onemkl/source/), a new [issue](https://github.com/uxlfoundation/oneAPI-spec/issues) with the \[RFC\] tag must be created to describe the API changes. The specification RFC must be reviewed by [UXL Foundation Math SIG forum](https://lists.uxlfoundation.org/g/Math-SIG), and only after it the proposed changes can be implemented in this project. 6. Merge PR when it has all required approvals * It's recommended to add PR number to the commit message, so it will be easy to find the design discussion