**Contributing to PyTorch: A Guide for First-Timers**

If you're new to contributing to PyTorch, we recommend starting with an issue at the easy level. This will give you a chance to get familiar with the process and learn from more experienced contributors. My colleagues will delve deeper into the specifics of how to locate, assign, and work on an issue, but before your first PR, you'll need to fill out the Contributor License Agreement (CLA) which will pop up before you submit your first PR. You'll also need to review the code of conduct, which can be found on the documentation for the particular repository you're contributing to.

All participants need to abide by the code of conduct, and we'll be using Discord for communication during the event in addition to commenting on PRs. This will allow us to stay connected and work together more effectively. We'll also have a kickoff event on Discord on June 4th at 10:00 AM Pacific, where we'll be having a live Q&A session to make things more exciting.

**PyTorch and PyTor Pytorch and PyTo tutorials contributions**

Sana here, I'm a documentation engineer on the Borch team. We're looking for contributions to the Borch and PyTorch tutorials. PyTorch has many functions that lack documentation, and we've identified a list of such functions that are frequently used by our team. We've created a task for each of these functions to document them. Apart from that, you'll find tasks from our regular backlog, as well as a small number of tasks that we haven't completed during the last Doon.

To get started, head over to the Daon H1 2024 issue in the PyTorch repository and read the instructions. There, you'll find information about the start and end date of the event, as well as who can participate. You'll also find that all issues for this Doon are marked with the "Doon H1 2024" label. This issue contains information about the difficulty labels, how to submit your PR, and so on.

In addition to these tutorials, we have a similar issue in most participating repositories. We have issues from our regular backlog as well as issues that require you to test the tutorials. These tutorials have lower than average ratings, and your task is to follow the instructions to test them and post your findings in the issue. Assign an issue to yourself, post a comment on the task, and then work on the issue.

**Contributions to Participating PyTorch Libraries**

Serge here, I'm a software engineer working on PyDeveloper Experience. As part of this Doon, we want to include a couple of projects from the PyTorch ecosystem outside of Cor PyTo. We want to motivate people to contribute to these repositories and not just to the main PyTorch repository.

Firstly, we're looking at Torch Fix, a code analysis tool that helps users of PyTorch follow best practices and keep their code in good shape. There's one issue on Torch Fix that includes multiple tasks, each task being about adding information about one particular Torch Fix rule to the README file. Every individual task should be relatively easy to complete, as most of the required information is already in the code comments. To claim a particular task, just comment on the issue that you want to work on it, then send a pull request to complete the task.

Bonus points will be awarded for any documentation-related issues you spot and all fixes in the Torch Fix repository.

Secondly, we're looking at PyTorch XCLA, which enables PyTorch on XCLA devices like Google Standard Processing Units. The p-slay repository is jointly operated and maintained by Google Meta, and individual contributors are encouraged to participate. The p-slay team has prepared a variety of interesting tasks, such as verifying examples, getting started documentation on various hardware, creating a glossary of common terms on the topic, adding new examples of running different deploying models, and improving documentation accessibility by updating diagrams to work in dark mode.

We're happy to have you participate and share your skills. Let's make meaningful contributions to the open-source ecosystem for the artificial intelligence Revolution!

"WEBVTTKind: captionsLanguage: enhello my name is Ivan and I'm a documentation engineer in the Pyro Team with me are spana and Sarge and we're here to welcome you to the pytorch Doon for H1 2024 we excited to have you join us in improving the documentation for pytorch and its related libraries this time around we'll be focusing on two main repositories that's the py to py to repo and the py to tutorials repo in addition we have some Library repositories like pyto xlaa and torch fix joining us for this event this is a great opportunity to learn about pytorch and its libraries and to contribute to the documentation the docon will start on June 4th and run for two weeks the final pull request or PR should be submitted by June 16th at 5:00 pm Pacific time issues will be posted on GitHub and participants are expected to assign an issue to themselves and submit a PR within a couple of days for review the issues are categorized into three levels of difficulty easy medium and advanced if this is your first time contributing to pytorch we recommend starting with an issue at the easy level my colleagues will delve deeper into the specifics of how to locate assign and work on an issue however before before you submit your first PR you will need to fill out the contributor license agreement CLA which will pop up before you submit your first PR you will also need to review the code of conduct which you can find on the docon issues in the particular repos so that is the py to pyto tutorials repos in GitHub all participants need to abide by the code of conduct we'll also be using Discord for communication during the event in addition to the comment on the PRS this will allow us to stay connected and work together more effectively we will also have a kickoff event on the Discord on June 4th at 10: a.m. Pacific so if you're watching this on June 4th at around 10 a.m. Pacific head over to the Discord and we'll be in there having a live kickoff event um and a q Q&A session to make things more exciting we'll be keeping track of contributions with a leaderboard top contributors will be recognized for their efforts so be sure to participate and share off your skills next I'll hand it over to Sana to talk more about the py toor pytorch and pytorch tutorials contributions Sana thanks Ian hi my name is Sana and I'm a documentation engineer on the borch team I'm going to walk you through the contributions we are looking for in the Bor borch and borch tutorials report by torch has many functions that lack documentation we have identified a list of such functions that they used frequently and create a task to document them apart from that you will find task from our regular backlog and a small number of tasks that we haven't completed during the last Doone to get started head over to the daon H1 2024 issue in the p p repo and read the instructions there you will find the information about the tone start and end date and who can participate you will also find that all the is issues for this docon are marked with the Doon H1 2024 label this issue contains information about the difficulty labels how to submit your PR and so on we have a similar issue in most participating repositories in the tutorial repo we have issues from our regular backlog as well as issues that require you to test the tutorials those tutorials have lower than average rating your task is to follow the instructions to test them and post your find in the issue to assign an issue to yourself post a assign to me comment on the task and you want to assign it to the one that you want to assign to yourself then you work on the issue and the BPR uh which we will review as soon as possible if you find an issue that is not actionable describe your findings in the issue and T tag one of us next Sergey will talk about the contributions we are looking for in the participating by torch libraries hi my name is Serge and I'm a software engineer working on P developer experience as it was said already for this Doon we want to include a couple of projects from the ptor ecosystem outside of cor pyto and to motivate people to contribute to these repositories and not just to the main py reer we will have the top top contributor for each of these projects recognized separately in addition to the overall contribution score the first of these repositories is torch fix the project I have created and currently maintaining torch fix is a code analysis tool basically a lter that helps users of pytorch to follow best practices and keep their code in a good shape for this docon there is one issue on touch fix that includes multiple tasks each task is about adding information about one particular T fix rule to the readme file every individual task should be relatively easy to complete as most of the required information should be already in the code comments to claim a particular task just comment on the issue that you want to work on it then send a pool request to complete the task bonus points for any documentation related issues you spot and all fix in the torch fix repository the second project for the Doon is pytorch xcla which enables pytorch on xcla devices like Google standard processing units the pic slay repository is jointly operated and maintained by Google meta and the number of individual contributors for this Doon the pic slay team prepared a variety of interesting tasks like verifying examples and getting started documentation on various Hardware creating a glossar of common terms on the topic adding new examples of running different deploying models and improving documentation accessibility by updating diagrams to work in dark mode so happy hacking and I hope you have some fun and get some experience while making meaningful contributions to the open source ecosystem for the artificial intelligence Revolutionhello my name is Ivan and I'm a documentation engineer in the Pyro Team with me are spana and Sarge and we're here to welcome you to the pytorch Doon for H1 2024 we excited to have you join us in improving the documentation for pytorch and its related libraries this time around we'll be focusing on two main repositories that's the py to py to repo and the py to tutorials repo in addition we have some Library repositories like pyto xlaa and torch fix joining us for this event this is a great opportunity to learn about pytorch and its libraries and to contribute to the documentation the docon will start on June 4th and run for two weeks the final pull request or PR should be submitted by June 16th at 5:00 pm Pacific time issues will be posted on GitHub and participants are expected to assign an issue to themselves and submit a PR within a couple of days for review the issues are categorized into three levels of difficulty easy medium and advanced if this is your first time contributing to pytorch we recommend starting with an issue at the easy level my colleagues will delve deeper into the specifics of how to locate assign and work on an issue however before before you submit your first PR you will need to fill out the contributor license agreement CLA which will pop up before you submit your first PR you will also need to review the code of conduct which you can find on the docon issues in the particular repos so that is the py to pyto tutorials repos in GitHub all participants need to abide by the code of conduct we'll also be using Discord for communication during the event in addition to the comment on the PRS this will allow us to stay connected and work together more effectively we will also have a kickoff event on the Discord on June 4th at 10: a.m. Pacific so if you're watching this on June 4th at around 10 a.m. Pacific head over to the Discord and we'll be in there having a live kickoff event um and a q Q&A session to make things more exciting we'll be keeping track of contributions with a leaderboard top contributors will be recognized for their efforts so be sure to participate and share off your skills next I'll hand it over to Sana to talk more about the py toor pytorch and pytorch tutorials contributions Sana thanks Ian hi my name is Sana and I'm a documentation engineer on the borch team I'm going to walk you through the contributions we are looking for in the Bor borch and borch tutorials report by torch has many functions that lack documentation we have identified a list of such functions that they used frequently and create a task to document them apart from that you will find task from our regular backlog and a small number of tasks that we haven't completed during the last Doone to get started head over to the daon H1 2024 issue in the p p repo and read the instructions there you will find the information about the tone start and end date and who can participate you will also find that all the is issues for this docon are marked with the Doon H1 2024 label this issue contains information about the difficulty labels how to submit your PR and so on we have a similar issue in most participating repositories in the tutorial repo we have issues from our regular backlog as well as issues that require you to test the tutorials those tutorials have lower than average rating your task is to follow the instructions to test them and post your find in the issue to assign an issue to yourself post a assign to me comment on the task and you want to assign it to the one that you want to assign to yourself then you work on the issue and the BPR uh which we will review as soon as possible if you find an issue that is not actionable describe your findings in the issue and T tag one of us next Sergey will talk about the contributions we are looking for in the participating by torch libraries hi my name is Serge and I'm a software engineer working on P developer experience as it was said already for this Doon we want to include a couple of projects from the ptor ecosystem outside of cor pyto and to motivate people to contribute to these repositories and not just to the main py reer we will have the top top contributor for each of these projects recognized separately in addition to the overall contribution score the first of these repositories is torch fix the project I have created and currently maintaining torch fix is a code analysis tool basically a lter that helps users of pytorch to follow best practices and keep their code in a good shape for this docon there is one issue on touch fix that includes multiple tasks each task is about adding information about one particular T fix rule to the readme file every individual task should be relatively easy to complete as most of the required information should be already in the code comments to claim a particular task just comment on the issue that you want to work on it then send a pool request to complete the task bonus points for any documentation related issues you spot and all fix in the torch fix repository the second project for the Doon is pytorch xcla which enables pytorch on xcla devices like Google standard processing units the pic slay repository is jointly operated and maintained by Google meta and the number of individual contributors for this Doon the pic slay team prepared a variety of interesting tasks like verifying examples and getting started documentation on various Hardware creating a glossar of common terms on the topic adding new examples of running different deploying models and improving documentation accessibility by updating diagrams to work in dark mode so happy hacking and I hope you have some fun and get some experience while making meaningful contributions to the open source ecosystem for the artificial intelligence Revolution\n"