# Core Maintainer Meeting Aug 15th, 2025 **URL:** \ **Category:** Uncategorized\ **Created:** [August 13, 2025, 10:49pm UTC](https://dev-discuss.pytorch.org/t/core-maintainer-meeting-aug-15th-2025/3182 "2025-08-13T22:49:39Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![gottbrath](https://yyz2.discourse-cdn.com/flex036/user_avatar/dev-discuss.pytorch.org/gottbrath/32/1043_2.png) [@gottbrath](https://dev-discuss.pytorch.org/u/gottbrath)\ **Post date:** [August 13, 2025, 10:49pm UTC](https://dev-discuss.pytorch.org/t/core-maintainer-meeting-aug-15th-2025/3182/1 "2025-08-13T22:49:39Z")
Our next PyTorch Core Maintainer Meeting is scheduled for Aug 15th. The general purpose of these meetings is to: - Discuss any technical plans and roadmaps for PyTorch - Review any high-level requests related to PyTorch, such as: - Creating new modules - Adding new maintainers at the core, module, or library level - Resolving any disputes among maintainers - PyTorch core maintainers are the primary attendees, with module maintainers and others invited only per meeting, depending on the agenda. The agenda for this meeting will be added to this post as it is developed and meeting minutes will be published to [dev-discuss.pytorch.org](http://dev-discuss.pytorch.org/). PyTorch Core Maintainers are: Soumith Chintala Edward Yang Gregory Chanan Dmytro Dzhulgakov Nikita Shulga Piotr Bialecki Alban Desmasion If you have any questions about PyTorch technical governance please refer to the information here: [Persons of Interest](https://pytorch.org/docs/main/community/persons_of_interest.html) [Governance Overview](https://pytorch.org/docs/stable/community/governance.html) The agenda is being developed right now. I’ll follow up to this post with the agenda for visibility. Any community member can propose agenda items by submitting them using the following link: [Form](https://share.hsforms.com/1fh3SpHFMR2ihEBQ2orgN8A4tvhy) ---
**Author:** ![gottbrath](https://yyz2.discourse-cdn.com/flex036/user_avatar/dev-discuss.pytorch.org/gottbrath/32/1043_2.png) [@gottbrath](https://dev-discuss.pytorch.org/u/gottbrath)\ **Post date:** [August 13, 2025, 10:51pm UTC](https://dev-discuss.pytorch.org/t/core-maintainer-meeting-aug-15th-2025/3182/2 "2025-08-13T22:51:56Z")
Current working agenda Agenda 1. Review and approve notes from last meeting 2. Tech topics - Switching to a more streamlined submission form - status update - PTF TAC looking for core maintainers (and other technical folks) to review and contribute to the certification they are creating. ![](https://canada1.discourse-cdn.com/flex036/uploads/pytorch1/original/2X/0/00239e89619fb3fbff4f96357de99b1569d83afb.jpeg) 1. Maintainer or core maintainer nominations received? - Mark O nominated as a pytorch/torchtune module maintainer ---
**Author:** ![gottbrath](https://yyz2.discourse-cdn.com/flex036/user_avatar/dev-discuss.pytorch.org/gottbrath/32/1043_2.png) [@gottbrath](https://dev-discuss.pytorch.org/u/gottbrath)\ **Post date:** [January 7, 2026, 12:18am UTC](https://dev-discuss.pytorch.org/t/core-maintainer-meeting-aug-15th-2025/3182/3 "2026-01-07T00:18:08Z")
These minutes from the Aug 15th meeting were approved in the Dec 5th core maintainers meeting Aug 15th meeting Core Maintainers: Soumith Chintala, Gregory Chanan, Edward Yang, Dmytro Dzhugakov,Alban Desmaison, Nikita Shulga, Piotr Bialecki Facilitator: Chris Gottbrath Discussion on the submission form - Why not email? - Alban offered that we could perhaps use a pytorch based gmail account. - Soumith : Just use a google form .. simple, move on. Reviewer of the certification - Nikita : Should we endorse the idea of certification at all? - Alban: There is a lot of demand .. so we could push back but that might be a bit of an uphill battle - Chris: we could establish standards and make sure that the materials meet those standards - Alban: I don’t want to write the certification book - Piotr: Have seen the requests as well. I volunteered to make sure that the information in the certification isn’t wrong - Greg: That makes sense. The thing I would want to be careful about is try to make sure that the core maintainers aren’t endorsing it, though one or more of the maintainers might also endorse. - Piotr: Review specifically around the GPU part - Chris: I think the ask was more for experts … than the core maintainers specifically endorsing the - Others: we don’t want to write the materials Roadmaps posted publicly - Nice that there was lots of attention - No particular discussion. Core maintainers for the projects that remain in the github pytorch org - What do we want to do for the domain libraries - Alban: Should we host things that are critical packages for the offering - Nikita: We should have a concrete list before we can make a decision - Alban: for items where there isn’t an organization that could take - Greg: potentially conflating things .. process for what stays and what doesn’t - Alban: I think it is a grey area .. and the foundation needs to know who to defer to - Nikita: are we uniquely suited to refer and find folks who could maintain the code - Alban: There are infra implications .. - Nikita: getting back to the main question: we should respond to the torchtune maintainer question .. and then also who would answer the question in a few months if torchtune remains in the foundation - Greg: I don’t think we should answer the question, at least now .. I don’t think we know what we [meta] want. - Alban: I think that makes some sense - Nikita: For torchvision – yes, we probably should keep - Greg: Proposes - Greg: - Alban: - Nikita: - Alban - Nikita - Alban - Chris - Remove merge right for metamates to prevent things like [REDACTED] - Alban - Greg - Nikita - Alban - Greg - Nikita - Greg - Piotr - Aban - Nikita - Summary FYI: Wheel variants is happening: [PyTorch 2.8 Live Release Q&A](https://www.youtube.com/watch?v=amx4zUyfl3I) 1. 10x smaller wheels AND better UX? Yes! - Alban: We need wheel variants not just for PyTorch but also for dependencies - Piotr: - Alban: - Nikita - Alban - Nikita - Alban - Nikita: - Piotr - Alban Nomination of [redacted] - Decision was to respond that “we are not the maintainers for Torchtune” - Advice Going forward