@PyTorch
Yesterday’s PyTorch 2.11 live Q&A with Nikita Shulga and Andrey Talman, moderated by Chris Gottbrath, covered five major focus areas: FlexAttention with FlashAttention-4, differentiable collectives, MPS operator expansion, RNN/LSTM GPU export support, and hardware backend improvements for AMD and Intel. A key topic of conversation was the influx of AI-generated code contributions and the specific framework maintainers use to protect repository integrity. Watch the clip below to see the discussion. Technical Policy on AI Contributions: 1. User owns the code: PyTorch treats the human submitter as the sole owner. Nikita Shulga stated that "User owns the code, not AI system" and maintainers will treat the contribution the same regardless of whether it comes through an AI agent or a person. 2. Called actionable: To preserve maintainer bandwidth, Nikita noted that contributions should focus on issues explicitly "called actionable." High-volume bursts, such as "fifty pull requests in an hour," are considered "disruptive behavior" and subject to temporary account blocks. 3. Test-driven development: PyTorch values "test-driven development." Nikita Shulga noted that if an AI contribution consists of "only fix," contributors will likely receive a comment to "please add a regression test" to verify the change against existing repository test structures. 4. First line of defense: Andrey Talman confirmed that the CI-CD system remains the "first line of defense," finding issues and ensuring code meets stability standards before it is accepted. Full video: https://t.co/kGiFS5N9RB #PyTorch #OpenSource #MachineLearning