From cca1bfa17518d003667471d6d212a0a070b51ee3 Mon Sep 17 00:00:00 2001 From: Svetlana Karslioglu Date: Thu, 8 Aug 2024 14:07:03 -0700 Subject: [PATCH 01/12] Create tutorial_submission_policy.md - Add a policy for new tutorials submissions --- tutorial_submission_policy.md | 64 +++++++++++++++++++++++++++++++++++ 1 file changed, 64 insertions(+) create mode 100644 tutorial_submission_policy.md diff --git a/tutorial_submission_policy.md b/tutorial_submission_policy.md new file mode 100644 index 00000000000..a0deb9b6288 --- /dev/null +++ b/tutorial_submission_policy.md @@ -0,0 +1,64 @@ +# PyTorch Tutorial Submission Policy + +This policy outlines the criteria and process for submitting new tutorials to the PyTorch community. +Our goal is to ensure that all tutorials are of high quality, relevant, and up-to-date, supporting +both the growth of our users and the evolution of the PyTorch framework itself. By following these +guidelines, contributors can help us maintain a robust and informative educational environment. + +## Acceptance Criteria For New Tutorials +We are committed to enhancing the learning experience for PyTorch users by providing high-quality +tutorials. We accept new tutorials that adhere to one of the following use cases: + +* **Support for New PyTorch Features:** Tutorials that support new features for upcoming PyTorch +releases are typically authored by the engineers who are developing these features. These tutorials +are crucial for showcasing the latest advancements in PyTorch. + +* **Tutorials from PyTorch Partners:** We welcome tutorials from our partners who are actively + collaborating with us to grow the PyTorch ecosystem. + +* **Direct Requests from PyTorch Maintainers:** If a PyTorch maintainer has directly reached out + to you to request a tutorial or otherwise, endorsed a tutorial, this indicates a specific need + within the community or the project. + +* **Tutorials from the open-source community members:** We accept tutorials from the community + members. However, as we can't accept all of them, we have identified the process below. + Please read below before sending a PR. + +The first three use cases do not require following the submission process described below. +If your tutorial falls under the fourth category, please read and follow the instructions in +the **Submission Process For Community-Contributed Tutorials** section. + +## Submission Process For Community-Contributed Tutorials + +To maintain the quality and relevance of tutorials, community-contributed tutorials must undergo +a review process. If you are interested in contributing a tutorial, please follow these steps: + +1. **Create an issue:** + * Open an issue in the pytorch/tutorials repository proposing the new tutorial. Clearly + explain the importance of the tutorial and confirm that there is no existing tutorial + covering the same or similar topic. A tutorial can't endorse one technology over another. + * These issues will be triaged by PyTorch maintainers on a case-by-case basis. + * Link any supporting materials including discussions in other repositories". + +1. **Await Approval:** + * Wait for a response from the PyTorch maintainers. They will review your proposal and + determine whether a tutorial on the proposed topic is desirable. **Do not submit a PR with + your tutorial** before you receive an approval. + +1. **Adhere to writing and styling guidelines:** + * Once approved, follow the guidelines outlined in [CONTRIBUTING.md](https://github.com/pytorch/tutorials/blob/main/CONTRIBUTING.md) + and use the provided [template](https://github.com/pytorch/tutorials/blob/main/beginner_source/template_tutorial.py) for creating your tutorial. + * Link the issue where you received an approval for your tutorial in the PR. + * We accept tutorials in both ``.rst`` (ReStructuredText) and ``.py`` (Python) + formats. However, unless your tutorial involves using multiple GPU, parallel/distributed + training, or requires extended execution time (25 minutes or more), we prefer submissions + in Python file format versus ``.rst``. + +1. **Maintenance:** + * By submitting a new tutorial, you agree to maintain it up-to-date with the latest PyTorch + updates and new features, review issues and pull requests and bugs submitted against the + tutorials and overall take proactive actions to ensure quality of the tutorial. + * Each tutorial must be updated by its owners at least once a year. Tutorials that are + abandoned by the owners will be eventually deprecated. + +We reserve the right to decline any new tutorial submissions that do not follow this policy. From 04e708c3f2b2f8bc235fb14884311a968a7b3d1c Mon Sep 17 00:00:00 2001 From: Svetlana Karslioglu Date: Thu, 8 Aug 2024 14:11:03 -0700 Subject: [PATCH 02/12] Add link in README.md --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 0c961afd262..162989dfe10 100644 --- a/README.md +++ b/README.md @@ -22,6 +22,8 @@ We use sphinx-gallery's [notebook styled examples](https://sphinx-gallery.github Here is how you can create a new tutorial (for a detailed description, see [CONTRIBUTING.md](./CONTRIBUTING.md)): +Before submitting a new tutorial read [PyTorch Tutorial Submission Policy](./tutorial_submission_policy.md) + 1. Create a Python file. If you want it executed while inserted into documentation, save the file with the suffix `tutorial` so that the file name is `your_tutorial.py`. 2. Put it in one of the `beginner_source`, `intermediate_source`, `advanced_source` directory based on the level of difficulty. If it is a recipe, add it to `recipes_source`. For tutorials demonstrating unstable prototype features, add to the `prototype_source`. 3. For Tutorials (except if it is a prototype feature), include it in the `toctree` directive and create a `customcarditem` in [index.rst](./index.rst). From 21d38517baa73573e4d331b3b2006ec4e34cac1d Mon Sep 17 00:00:00 2001 From: Svetlana Karslioglu Date: Thu, 8 Aug 2024 14:11:50 -0700 Subject: [PATCH 03/12] Typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 162989dfe10..fe4b4b6edd6 100644 --- a/README.md +++ b/README.md @@ -22,7 +22,7 @@ We use sphinx-gallery's [notebook styled examples](https://sphinx-gallery.github Here is how you can create a new tutorial (for a detailed description, see [CONTRIBUTING.md](./CONTRIBUTING.md)): -Before submitting a new tutorial read [PyTorch Tutorial Submission Policy](./tutorial_submission_policy.md) +NOTE: Before submitting a new tutorial, read [PyTorch Tutorial Submission Policy](./tutorial_submission_policy.md). 1. Create a Python file. If you want it executed while inserted into documentation, save the file with the suffix `tutorial` so that the file name is `your_tutorial.py`. 2. Put it in one of the `beginner_source`, `intermediate_source`, `advanced_source` directory based on the level of difficulty. If it is a recipe, add it to `recipes_source`. For tutorials demonstrating unstable prototype features, add to the `prototype_source`. From e0d50beaf597dc820fd7c614f32b66db16179b3e Mon Sep 17 00:00:00 2001 From: Svetlana Karslioglu Date: Thu, 22 Aug 2024 12:49:44 -0700 Subject: [PATCH 04/12] Address comments --- tutorial_submission_policy.md | 137 ++++++++++++++++++++++------------ 1 file changed, 91 insertions(+), 46 deletions(-) diff --git a/tutorial_submission_policy.md b/tutorial_submission_policy.md index a0deb9b6288..58e0893f33d 100644 --- a/tutorial_submission_policy.md +++ b/tutorial_submission_policy.md @@ -1,64 +1,109 @@ # PyTorch Tutorial Submission Policy -This policy outlines the criteria and process for submitting new tutorials to the PyTorch community. -Our goal is to ensure that all tutorials are of high quality, relevant, and up-to-date, supporting -both the growth of our users and the evolution of the PyTorch framework itself. By following these -guidelines, contributors can help us maintain a robust and informative educational environment. +This policy outlines the criteria and process for submitting new +tutorials to the PyTorch community. +Our goal is to ensure that all tutorials are of high quality, +relevant, and up-to-date, supporting both the growth of the PyTorch +users and the evolution of the PyTorch framework itself. By following +these guidelines, contributors can help us maintain a robust and +informative educational environment. ## Acceptance Criteria For New Tutorials -We are committed to enhancing the learning experience for PyTorch users by providing high-quality -tutorials. We accept new tutorials that adhere to one of the following use cases: - -* **Support for New PyTorch Features:** Tutorials that support new features for upcoming PyTorch -releases are typically authored by the engineers who are developing these features. These tutorials -are crucial for showcasing the latest advancements in PyTorch. - -* **Tutorials from PyTorch Partners:** We welcome tutorials from our partners who are actively - collaborating with us to grow the PyTorch ecosystem. - -* **Direct Requests from PyTorch Maintainers:** If a PyTorch maintainer has directly reached out - to you to request a tutorial or otherwise, endorsed a tutorial, this indicates a specific need - within the community or the project. - -* **Tutorials from the open-source community members:** We accept tutorials from the community - members. However, as we can't accept all of them, we have identified the process below. - Please read below before sending a PR. - -The first three use cases do not require following the submission process described below. -If your tutorial falls under the fourth category, please read and follow the instructions in -the **Submission Process For Community-Contributed Tutorials** section. + +We accept new tutorials that adhere to one of the following use cases: + +* **Support for New PyTorch Features:** Tutorials that support new features + for upcoming PyTorch releases are typically authored by the engineers who + are developing these features. These tutorials are crucial for showcasing + the latest advancements in PyTorch. We typically don't require more than + one tutorial per feature. + +* **Tutorials showcasing PyTorch usage with other tools and libraries:** We + accept community-contributed tutorials that illustrate innovative uses of + PyTorch alongside other open-source projects, models, and tools. Please + ensure that your tutorial remains neutral and does not promote or endorse + proprietary technologies over others. + +The first use case does not require going through the submission +process outlined below. If your tutorial falls under the second category, +please read and follow the instructions in the +**Submission Process For Community-Contributed Tutorials** section. ## Submission Process For Community-Contributed Tutorials -To maintain the quality and relevance of tutorials, community-contributed tutorials must undergo -a review process. If you are interested in contributing a tutorial, please follow these steps: +To maintain the quality and relevance of tutorials, we request that +community-contributed tutorials undergo a review process. If you are +interested in contributing a tutorial, please follow these steps: 1. **Create an issue:** - * Open an issue in the pytorch/tutorials repository proposing the new tutorial. Clearly - explain the importance of the tutorial and confirm that there is no existing tutorial - covering the same or similar topic. A tutorial can't endorse one technology over another. + * Open an issue in the pytorch/tutorials repository proposing the + new tutorial. Clearly explain the importance of the tutorial and + confirm that there is no existing tutorial covering the same or + similar topic. A tutorial should not disproportionately endorse + one technology over another. Please consult with Core Maintainers + to ensure your content adheres to these guidelines. + Use the provided `ISSUE_TEMPLATE` for the new tutorial request. + + * If there is a tutorial on the existing topic that you would like + to significantly refactor, you can just submit a PR. In the + description of the PR explain why the changes are needed and + how they improve the tutorial. + * These issues will be triaged by PyTorch maintainers on a case-by-case basis. - * Link any supporting materials including discussions in other repositories". + * Link any supporting materials including discussions in other repositories. 1. **Await Approval:** - * Wait for a response from the PyTorch maintainers. They will review your proposal and - determine whether a tutorial on the proposed topic is desirable. **Do not submit a PR with - your tutorial** before you receive an approval. + * Wait for a response from the PyTorch maintainers. A PyTorch + tutorial maintainer will review your proposal and + determine whether a tutorial on the proposed topic is desirable. + A comment and an **approved** label will be added to your tutorial + by a maintainer. Review process for new tutorial PRs submitted + without the corresponding issue will take longer. 1. **Adhere to writing and styling guidelines:** * Once approved, follow the guidelines outlined in [CONTRIBUTING.md](https://github.com/pytorch/tutorials/blob/main/CONTRIBUTING.md) and use the provided [template](https://github.com/pytorch/tutorials/blob/main/beginner_source/template_tutorial.py) for creating your tutorial. - * Link the issue where you received an approval for your tutorial in the PR. - * We accept tutorials in both ``.rst`` (ReStructuredText) and ``.py`` (Python) - formats. However, unless your tutorial involves using multiple GPU, parallel/distributed - training, or requires extended execution time (25 minutes or more), we prefer submissions + * Link the issue in which you received an approval for your tutorial + in the PR. + * We accept tutorials in both ``.rst`` (ReStructuredText) and ``.py`` + (Python) formats. However, unless your tutorial involves using + multiple GPU, parallel/distributed training, or requires extended + execution time (25 minutes or more), we prefer submissions in Python file format versus ``.rst``. -1. **Maintenance:** - * By submitting a new tutorial, you agree to maintain it up-to-date with the latest PyTorch - updates and new features, review issues and pull requests and bugs submitted against the - tutorials and overall take proactive actions to ensure quality of the tutorial. - * Each tutorial must be updated by its owners at least once a year. Tutorials that are - abandoned by the owners will be eventually deprecated. - -We reserve the right to decline any new tutorial submissions that do not follow this policy. +## Maintening Tutorials + +When you submit a new tutorial, we encourage you to keep it updated +with the latest PyTorch updates and features. Additionally, we may +contact you to review any PRs, issues, and other related matters to +ensure the tutorial remains a valuable resource. + +Please note the following: + +* If a tutorial is broken against the main branch, the tutorial will + be excluded from the build and an issue will be filed against it + with the author/maintainer notified about the issue. If the issue + is not resolved within 90 days, the tutorial might be deleted from + the repository. + +* We recommend that each tutorial is reviewed at least once a year to + ensure its relevance. + +## Deleting Stale Tutorials + +A tutorial might be considered stale when it has not been updated for +a significant period (more than a year) and no longer aligns with the +latest PyTorch updates, features, or best practices. Other indicators +of a stale tutorial include: + +* The tutorial is no longer functional due to changes in PyTorch or + its dependencies +* The tutorial has been superseded by a newer, more comprehensive, or + more accurate tutorial +* The tutorial does not run successfully in the (CI), indicating + potential compatibility or dependency issues. + +If a tutorial is deemed stale, we will attempt to contact the code owner +or someone from the tutorial mainatainers might attempt to update it. +However, if despite those attempts, we fail to fix it, the tutorial +might be removed from the repository. From ce79b608e8a8d30971aaf79f5145eee3b438c7b1 Mon Sep 17 00:00:00 2001 From: Svetlana Karslioglu Date: Fri, 23 Aug 2024 12:54:49 -0700 Subject: [PATCH 05/12] Update tutorial_submission_policy.md Co-authored-by: albanD --- tutorial_submission_policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorial_submission_policy.md b/tutorial_submission_policy.md index 58e0893f33d..3a518862559 100644 --- a/tutorial_submission_policy.md +++ b/tutorial_submission_policy.md @@ -69,7 +69,7 @@ interested in contributing a tutorial, please follow these steps: (Python) formats. However, unless your tutorial involves using multiple GPU, parallel/distributed training, or requires extended execution time (25 minutes or more), we prefer submissions - in Python file format versus ``.rst``. + in Python file format. ## Maintening Tutorials From 193b58175bef13cadc6df6e589a69def2a1ff137 Mon Sep 17 00:00:00 2001 From: Svetlana Karslioglu Date: Fri, 23 Aug 2024 13:09:09 -0700 Subject: [PATCH 06/12] Update tutorial_submission_policy.md --- tutorial_submission_policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorial_submission_policy.md b/tutorial_submission_policy.md index 3a518862559..3a8d1a5273f 100644 --- a/tutorial_submission_policy.md +++ b/tutorial_submission_policy.md @@ -12,7 +12,7 @@ informative educational environment. We accept new tutorials that adhere to one of the following use cases: -* **Support for New PyTorch Features:** Tutorials that support new features +* **Demonstrate New PyTorch Features:** Tutorials that support new features for upcoming PyTorch releases are typically authored by the engineers who are developing these features. These tutorials are crucial for showcasing the latest advancements in PyTorch. We typically don't require more than From 0f2fa13345a151291a94490fc7c861ee5cd3d059 Mon Sep 17 00:00:00 2001 From: Svetlana Karslioglu Date: Fri, 23 Aug 2024 13:56:50 -0700 Subject: [PATCH 07/12] Update tutorial_submission_policy.md Co-authored-by: Nikita Shulga <2453524+malfet@users.noreply.github.com> --- tutorial_submission_policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorial_submission_policy.md b/tutorial_submission_policy.md index 3a8d1a5273f..01c7eba6c16 100644 --- a/tutorial_submission_policy.md +++ b/tutorial_submission_policy.md @@ -53,7 +53,7 @@ interested in contributing a tutorial, please follow these steps: * Link any supporting materials including discussions in other repositories. 1. **Await Approval:** - * Wait for a response from the PyTorch maintainers. A PyTorch + * Wait for a response from the PyTorch Tutorials maintainers. A PyTorch tutorial maintainer will review your proposal and determine whether a tutorial on the proposed topic is desirable. A comment and an **approved** label will be added to your tutorial From 69229f962ee0a6fb069a9618cd1480e70eb41d2f Mon Sep 17 00:00:00 2001 From: Svetlana Karslioglu Date: Fri, 23 Aug 2024 13:57:07 -0700 Subject: [PATCH 08/12] Update tutorial_submission_policy.md Co-authored-by: Nikita Shulga <2453524+malfet@users.noreply.github.com> --- tutorial_submission_policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorial_submission_policy.md b/tutorial_submission_policy.md index 01c7eba6c16..61a23353ef1 100644 --- a/tutorial_submission_policy.md +++ b/tutorial_submission_policy.md @@ -71,7 +71,7 @@ interested in contributing a tutorial, please follow these steps: execution time (25 minutes or more), we prefer submissions in Python file format. -## Maintening Tutorials +## Maintaining Tutorials When you submit a new tutorial, we encourage you to keep it updated with the latest PyTorch updates and features. Additionally, we may From 8e4544803e998e2e85d8dd318988764b35e58670 Mon Sep 17 00:00:00 2001 From: Svetlana Karslioglu Date: Fri, 23 Aug 2024 13:59:19 -0700 Subject: [PATCH 09/12] Update tutorial_submission_policy.md --- tutorial_submission_policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorial_submission_policy.md b/tutorial_submission_policy.md index 61a23353ef1..7f12dc5f94a 100644 --- a/tutorial_submission_policy.md +++ b/tutorial_submission_policy.md @@ -42,7 +42,7 @@ interested in contributing a tutorial, please follow these steps: similar topic. A tutorial should not disproportionately endorse one technology over another. Please consult with Core Maintainers to ensure your content adheres to these guidelines. - Use the provided `ISSUE_TEMPLATE` for the new tutorial request. + Use the provided [ISSUE_TEMPLATE](https://github.com/pytorch/tutorials/blob/main/.github/ISSUE_TEMPLATE/feature-request.yml) for the new tutorial request - select **Feature request** when submitting an issue. . * If there is a tutorial on the existing topic that you would like to significantly refactor, you can just submit a PR. In the From 93e7ce33cdc989616bd1ff62de1c8f3e54c795de Mon Sep 17 00:00:00 2001 From: Svetlana Karslioglu Date: Fri, 23 Aug 2024 15:20:32 -0700 Subject: [PATCH 10/12] Update tutorial_submission_policy.md Co-authored-by: Nikita Shulga <2453524+malfet@users.noreply.github.com> --- tutorial_submission_policy.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/tutorial_submission_policy.md b/tutorial_submission_policy.md index 7f12dc5f94a..8c3290f827a 100644 --- a/tutorial_submission_policy.md +++ b/tutorial_submission_policy.md @@ -91,10 +91,7 @@ Please note the following: ## Deleting Stale Tutorials -A tutorial might be considered stale when it has not been updated for -a significant period (more than a year) and no longer aligns with the -latest PyTorch updates, features, or best practices. Other indicators -of a stale tutorial include: +A tutorial might be considered stale when it no longer aligns with the latest PyTorch updates, features, or best practices or: * The tutorial is no longer functional due to changes in PyTorch or its dependencies From c7915569856910e5257317e2d1a25183854c54fa Mon Sep 17 00:00:00 2001 From: Svetlana Karslioglu Date: Fri, 23 Aug 2024 15:36:56 -0700 Subject: [PATCH 11/12] Address comments, fix typos --- tutorial_submission_policy.md | 35 ++++++++++++++++++----------------- 1 file changed, 18 insertions(+), 17 deletions(-) diff --git a/tutorial_submission_policy.md b/tutorial_submission_policy.md index 8c3290f827a..7edaa3bdb67 100644 --- a/tutorial_submission_policy.md +++ b/tutorial_submission_policy.md @@ -15,7 +15,7 @@ We accept new tutorials that adhere to one of the following use cases: * **Demonstrate New PyTorch Features:** Tutorials that support new features for upcoming PyTorch releases are typically authored by the engineers who are developing these features. These tutorials are crucial for showcasing - the latest advancements in PyTorch. We typically don't require more than + the latest advancements in PyTorch. We typically do not require more than one tutorial per feature. * **Tutorials showcasing PyTorch usage with other tools and libraries:** We @@ -44,9 +44,9 @@ interested in contributing a tutorial, please follow these steps: to ensure your content adheres to these guidelines. Use the provided [ISSUE_TEMPLATE](https://github.com/pytorch/tutorials/blob/main/.github/ISSUE_TEMPLATE/feature-request.yml) for the new tutorial request - select **Feature request** when submitting an issue. . - * If there is a tutorial on the existing topic that you would like - to significantly refactor, you can just submit a PR. In the - description of the PR explain why the changes are needed and + * If there is an existing tutorial on the topic that you would + like to significantly refactor, you can submit a PR. In the + description of the PR, explain why the changes are needed and how they improve the tutorial. * These issues will be triaged by PyTorch maintainers on a case-by-case basis. @@ -56,14 +56,14 @@ interested in contributing a tutorial, please follow these steps: * Wait for a response from the PyTorch Tutorials maintainers. A PyTorch tutorial maintainer will review your proposal and determine whether a tutorial on the proposed topic is desirable. - A comment and an **approved** label will be added to your tutorial - by a maintainer. Review process for new tutorial PRs submitted - without the corresponding issue will take longer. + A comment and an **approved** label will be added to your issue + by a maintainer. The review process for new tutorial PRs submitted + without the corresponding issue may take longer. 1. **Adhere to writing and styling guidelines:** * Once approved, follow the guidelines outlined in [CONTRIBUTING.md](https://github.com/pytorch/tutorials/blob/main/CONTRIBUTING.md) and use the provided [template](https://github.com/pytorch/tutorials/blob/main/beginner_source/template_tutorial.py) for creating your tutorial. - * Link the issue in which you received an approval for your tutorial + * Link the issue in which you received approval for your tutorial in the PR. * We accept tutorials in both ``.rst`` (ReStructuredText) and ``.py`` (Python) formats. However, unless your tutorial involves using @@ -73,25 +73,26 @@ interested in contributing a tutorial, please follow these steps: ## Maintaining Tutorials -When you submit a new tutorial, we encourage you to keep it updated +When you submit a new tutorial, we encourage you to keep it in sync with the latest PyTorch updates and features. Additionally, we may contact you to review any PRs, issues, and other related matters to ensure the tutorial remains a valuable resource. Please note the following: -* If a tutorial is broken against the main branch, the tutorial will - be excluded from the build and an issue will be filed against it - with the author/maintainer notified about the issue. If the issue - is not resolved within 90 days, the tutorial might be deleted from - the repository. +* If a tutorial breaks against the main branch, it will + be excluded from the build and an issue will be filed against it, + with the author/maintainer notified. If the issue is not resolved + within 90 days, the tutorial might be deleted from the repository. * We recommend that each tutorial is reviewed at least once a year to ensure its relevance. ## Deleting Stale Tutorials -A tutorial might be considered stale when it no longer aligns with the latest PyTorch updates, features, or best practices or: +A tutorial might be considered stale when it no longer aligns with +the latest PyTorch updates, features, or best practices or best +practices: * The tutorial is no longer functional due to changes in PyTorch or its dependencies @@ -100,7 +101,7 @@ A tutorial might be considered stale when it no longer aligns with the latest Py * The tutorial does not run successfully in the (CI), indicating potential compatibility or dependency issues. -If a tutorial is deemed stale, we will attempt to contact the code owner +If a tutorial is deemed stale, we will attempt to contact the code owner, or someone from the tutorial mainatainers might attempt to update it. -However, if despite those attempts, we fail to fix it, the tutorial +However, if despite those attempts we fail to fix it, the tutorial might be removed from the repository. From 3930f092b4d27f22528d5466afdf9fb50d559afa Mon Sep 17 00:00:00 2001 From: Nikita Shulga <2453524+malfet@users.noreply.github.com> Date: Sat, 24 Aug 2024 11:13:18 -0700 Subject: [PATCH 12/12] Update tutorial_submission_policy.md --- tutorial_submission_policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorial_submission_policy.md b/tutorial_submission_policy.md index 7edaa3bdb67..c5c3a800876 100644 --- a/tutorial_submission_policy.md +++ b/tutorial_submission_policy.md @@ -42,7 +42,7 @@ interested in contributing a tutorial, please follow these steps: similar topic. A tutorial should not disproportionately endorse one technology over another. Please consult with Core Maintainers to ensure your content adheres to these guidelines. - Use the provided [ISSUE_TEMPLATE](https://github.com/pytorch/tutorials/blob/main/.github/ISSUE_TEMPLATE/feature-request.yml) for the new tutorial request - select **Feature request** when submitting an issue. . + Use the provided [ISSUE_TEMPLATE](https://github.com/pytorch/tutorials/blob/main/.github/ISSUE_TEMPLATE/feature-request.yml) for the new tutorial request - select **Feature request** when submitting an issue. * If there is an existing tutorial on the topic that you would like to significantly refactor, you can submit a PR. In the