Lightning Governance¶
This document describes governance processes we follow in developing PyTorch Lightning.
Persons of Interest¶
BDFL¶
Role: All final decisions related to Lightning.
William Falcon (williamFalcon) (Lightning founder)
Maintainers¶
Luca Antiga (lantiga)
Jirka Borovec (Borda)
Justus Schock (justusschock)
Emeritus Maintainers¶
Ethan Harris (ethanwharris) (Torchbearer founder)
Nicki Skafte (SkafteNicki)
Thomas Chaton (tchaton)
Alumni¶
Adrian Wälchli (awaelchli)
Carlos Mocholí (carmocca)
Akihiro Nitta (akihironitta)
Ananth Subramaniam (ananthsub)
Danielle Pintz (daniellepintz)
Jeff Ling (jeffling)
Jeff Yang (ydcjeff)
Jeremy Jordan (jeremyjordan)
Kaushik Bokka (kaushikb11)
Kushashwa Ravi Shrimali (krshrimali)
Lezwon Castelino (lezwon)
Matthew Painter (MattPainter01) (Torchbearer founder)
Nate Raw (nateraw)
Nic Eggert (neggert)
Ota Jasek (otaj)
Peter Yu (yukw777)
Roger Shieh (s-rog)
Rohit Gupta (rohitgr7)
Sean Narenthiran (SeanNaren)
Siyu Wang (four4fish)
Teddy Koker (teddykoker)
Tullie Murrell (tullie)
Project Management and Decision Making¶
The decision what goes into a release is governed by the maintainers of lightning.pytorch.
Whenever possible, discussion happens publicly on GitHub and includes the whole community.
For controversial changes, it is mandatory to seek consultation from BDFL for a final decision.
When a consensus is reached, maintainers assign milestones and labels to the issue and/or pull request
and start tracking the development. It is possible that priorities change over time.
Commits to the project are exclusively to be added by pull requests on GitHub and anyone in the community is welcome to review them. However, reviews submitted by code owners have higher weight and it is necessary to get the approval of code owners before a pull request can be merged. Additional requirements may apply case by case.
