From 8813ac956e93382eb06d7e79ca3bbd930a78e7af Mon Sep 17 00:00:00 2001 From: Maria Kraynyuk Date: Mon, 12 Aug 2024 10:36:02 -0700 Subject: [PATCH] contributing: add a link to RFC branch --- CONTRIBUTING.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 9a41383bd..9cab67da4 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -7,7 +7,7 @@ For how to enable a new third-party library, see the [guidelines](docs/create_ne Before sending your pull requests, ensure that you follow this checklist: -* If you are contributing a new interface, refer to the [library functionality guidelines](CONTRIBUTING.md#library-functionality-guidelines). It is strongly advised that you first open an [RFC issue](CONTRIBUTING.md#RFC-issue) with a detailed explanation of the expected use cases. +* If you are contributing a new interface, refer to the [library functionality guidelines](CONTRIBUTING.md#library-functionality-guidelines). It is strongly advised that you first open an [RFC PR](CONTRIBUTING.md#RFC-process) with a detailed explanation of the expected use cases. * Ensure that your code includes proper documentation. @@ -32,9 +32,12 @@ oneMKL focuses on the following criteria: For the new API to become a part of the open source project, it should be accepted as part of [oneMKL spec](https://spec.oneapi.com/versions/latest/elements/oneMKL/source/index.html). -### RFC Issue +### RFC Process -Open a Request For Comment (RFC) issue when contributing new interfaces. In the RFC, please provide the following details: +For changes impacting the public API or any significant changes in the library, such as adding new backend or changes to the architecture, +please follow the [RFC process](https://github.com/oneapi-src/oneMKL/tree/rfcs). + +Please also provide the following details as part of the RFC: * Description of how the new interface meets [library functionality guidelines](CONTRIBUTING.md#library-functionality-guidelines).