PyTorch Core Maintainers Meeting

1

Our next PyTorch Core Maintainer Meeting is scheduled for May 2nd.

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.

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
Governance Overview

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

2

Not sure how I missed posting these notes from the May core maintainers meeting.

These notes are from the May 2nd meeting and were reviewed and approved in the Aug 15th session.

Core Maintainers: Soumith Chintala, Gregory Chanan, Edward Yang, Dmytro Dzhugakov,Alban Desmaison, Nikita Shulga, Piotr Bialecki

Facilitator: Chris Gottbrath

Agenda:

Review and approve notes (what is said and what is redacted) from last meeting

Tech topics ?

  • Chris: Just flagging that there may be some signal being missed with the topic / nomination submission form that PTF provides.

Form is

The form is referenced here https://github.com/pytorch/pytorch/blob/b11c9e1808484f52e01cebf639691e62ea2b6311/docs/source/community/governance.rst#L4

The last two times I asked the PTF folks for any submissions that had come in they didn’t provide any.

It isn’t clear they know where the form data is being saved.

I did put in a test submission, which they should have found and sent back to me.

Current ask is for Soumith and I to get emails each time a form submission is made.

Latest discussion is if this should be done through github vs hubspot.

Maintainer or core maintainer nominations received?

   I haven’t seen any

Notes

1st issue: Hugging Face performance regression

  • Piotr:

    • Huggingface pinned to an earlier version after the 2.7 release due to a claimed 10x slowdown

      • We don’t have a full root cause / analysis of the tech situation

    • Would be nice to have a better communication channel around the release

  • Nikita

    • We have a slack with Hugging Face .. but is that enough?

    • We could suggest that ecosystem partners (like Hugging Face) run tests against the “to be released” version.

  • Alban:

    • Is there a communication issue

  • Piotr:

    • Heard something that suggested Hugging Face was aware of the regression (something like “there is something weird here”)

    • That suggests that it is a communication issue

  • Alban

    • Ping on the hugging face / PyTorch channel when we create RCs

  • Nikita

    • Problem was that they didn’t communicate back that they were seeing the regression

  • Take away

    • Pick a set of programs that we care about and coordinate with them during the release candidate process

    • Reach out to huggingface to tell them to be more vocal

The submission form item

Action item for Chris G:

  • Switch with a google form that we control

Nikita: 2025 is when we are supposed to transfer PyTorch Github to LF

Nikita:

  • Concern about what might happen

  • LF aren’t showing good discipline about who they add to the repository

Soumith

  • What are you proposing .. delay the github transfer by 6 months or a year

Nikita:

  • Yes,

  • We have a lot of projects under the organization .. which are in different states

Soumith

  • Joe Spisak shared that they have a good process for accepting projects under the umbrella

  • Matt White doesn’t have full visibility to what is happening

Nikita

  • WE have a 200 projects

Alban

  • 55 public, 110 total

Soumith

  • We could just grandfather in all the projects in the PyTorch org when we transfer to the PTF

Nikita

  • Yea that sounds ok

AI: Chris - Nikita will tag all the public project with a company name

Pierre and Joe .. that we want to have a grandfathering agreement that the project will hosted but without having any governance change. Ownership will stay with the company.

Then they have a 3 year deadline to move out if they don’t want to comply with the governance

Nikita

  • Core maintainers need to be admins for the github

Soumith

  • There is a concern that a former maintainer might work against the interest of the organization

Alban

  • Why do we think LF wouldn’t go rogue

Soumith

  • They aren’t going to be as personally connected

Alban

  • For security related issues .. we should have a way to fix something quickly

Soumith

  • Can we set up a way so that 2 (designated) core maintainers could get access for the emergency fix type scenarios

    • (two factor based authentication)

  • Thinks the board would probably be ok with this. We should propose something

AI: Nikita to write up a proposal on how this could work. Circulate this first with this group and then go

Nikita: CV filed against PyTorch

Nikita:

  • There is a mechanism CMA that we can use to “vet” the submitted security issues that are reported to CVE.

  • If security.pytorch.org exists we can use that as the address for this.

AI: Nikita to continue this process

Alban: Wiki is completely open and someone tried to take it over

Alban:

  • We fixed it

  • We put the wiki in a better state so that it can’t so easily been taken over.

  • Fixed some other repos (meta owned and OSS general)

Nikita:

  • Linux foundation also seemed perplexed about this
1 Like