VOTE: Moving pip-tools to PyPA
Hi PyPA committers, I'd like to open a vote on transferring pip-tools to the PyPA GitHub org: https://github.com/jazzband/pip-tools This is a project that provides a way to generate constraint files and manage virtualenv pins. Sometimes, I call it "an early DIY lock files" implementation. It's used by Dependabot to upgrade requirement/constraint files and is a prior art for what's reimplemented in uv. It's spent most of its life in the Jazzband collaborative maintenance organisation that is getting shut down this year[1]. And so, naturally we're looking for a new home[2]. Since both Stephen and I (webknjaz and sirosen — the current project leads) are already a part of PyPA and it is a tool of the packaging realm, we feel it's a good idea to keep maintaining the project under the familiar umbrella. -- Warm regards, Sviatoslav Sydorenko [1]: https://github.com/jazzband/pip-tools/discussions/2353 [2]: https://jazzband.co/news/2026/03/14/sunsetting-jazzband
+1 On Thu, Mar 19, 2026, 18:50 Sviatoslav Sydorenko via PyPA-Committers < pypa-committers@python.org> wrote:
Hi PyPA committers,
I'd like to open a vote on transferring pip-tools to the PyPA GitHub org:
https://github.com/jazzband/pip-tools
This is a project that provides a way to generate constraint files and manage virtualenv pins. Sometimes, I call it "an early DIY lock files" implementation. It's used by Dependabot to upgrade requirement/constraint files and is a prior art for what's reimplemented in uv.
It's spent most of its life in the Jazzband collaborative maintenance organisation that is getting shut down this year[1]. And so, naturally we're looking for a new home[2]. Since both Stephen and I (webknjaz and sirosen — the current project leads) are already a part of PyPA and it is a tool of the packaging realm, we feel it's a good idea to keep maintaining the project under the familiar umbrella.
-- Warm regards, Sviatoslav Sydorenko
[1]: https://github.com/jazzband/pip-tools/discussions/2353
[2]: https://jazzband.co/news/2026/03/14/sunsetting-jazzband _______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3//lists/pypa-committers.python.org Member address: miketheman@gmail.com
+1 from me! Paul On Thu, 19 Mar 2026 at 22:50, Sviatoslav Sydorenko via PyPA-Committers < pypa-committers@python.org> wrote:
Hi PyPA committers,
I'd like to open a vote on transferring pip-tools to the PyPA GitHub org:
https://github.com/jazzband/pip-tools
This is a project that provides a way to generate constraint files and manage virtualenv pins. Sometimes, I call it "an early DIY lock files" implementation. It's used by Dependabot to upgrade requirement/constraint files and is a prior art for what's reimplemented in uv.
It's spent most of its life in the Jazzband collaborative maintenance organisation that is getting shut down this year[1]. And so, naturally we're looking for a new home[2]. Since both Stephen and I (webknjaz and sirosen — the current project leads) are already a part of PyPA and it is a tool of the packaging realm, we feel it's a good idea to keep maintaining the project under the familiar umbrella.
-- Warm regards, Sviatoslav Sydorenko
[1]: https://github.com/jazzband/pip-tools/discussions/2353
[2]: https://jazzband.co/news/2026/03/14/sunsetting-jazzband _______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3//lists/pypa-committers.python.org Member address: p.f.moore@gmail.com
+1 On Thu, Mar 19, 2026 at 17:07 Paul Moore via PyPA-Committers < pypa-committers@python.org> wrote:
+1 from me!
Paul
On Thu, 19 Mar 2026 at 22:50, Sviatoslav Sydorenko via PyPA-Committers < pypa-committers@python.org> wrote:
Hi PyPA committers,
I'd like to open a vote on transferring pip-tools to the PyPA GitHub org:
https://github.com/jazzband/pip-tools
This is a project that provides a way to generate constraint files and manage virtualenv pins. Sometimes, I call it "an early DIY lock files" implementation. It's used by Dependabot to upgrade requirement/constraint files and is a prior art for what's reimplemented in uv.
It's spent most of its life in the Jazzband collaborative maintenance organisation that is getting shut down this year[1]. And so, naturally we're looking for a new home[2]. Since both Stephen and I (webknjaz and sirosen — the current project leads) are already a part of PyPA and it is a tool of the packaging realm, we feel it's a good idea to keep maintaining the project under the familiar umbrella.
-- Warm regards, Sviatoslav Sydorenko
[1]: https://github.com/jazzband/pip-tools/discussions/2353
[2]: https://jazzband.co/news/2026/03/14/sunsetting-jazzband _______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3//lists/pypa-committers.python.org Member address: p.f.moore@gmail.com
_______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3//lists/pypa-committers.python.org Member address: nate.prewitt@gmail.com
+1 from me. Yours, Russ Magee %-)
On 20 Mar 2026, at 6:50 am, Sviatoslav Sydorenko via PyPA-Committers <pypa-committers@python.org> wrote:
Hi PyPA committers,
I'd like to open a vote on transferring pip-tools to the PyPA GitHub org:
https://github.com/jazzband/pip-tools
This is a project that provides a way to generate constraint files and manage virtualenv pins. Sometimes, I call it "an early DIY lock files" implementation. It's used by Dependabot to upgrade requirement/constraint files and is a prior art for what's reimplemented in uv.
It's spent most of its life in the Jazzband collaborative maintenance organisation that is getting shut down this year[1]. And so, naturally we're looking for a new home[2]. Since both Stephen and I (webknjaz and sirosen — the current project leads) are already a part of PyPA and it is a tool of the packaging realm, we feel it's a good idea to keep maintaining the project under the familiar umbrella.
-- Warm regards, Sviatoslav Sydorenko
[1]: https://github.com/jazzband/pip-tools/discussions/2353
[2]: https://jazzband.co/news/2026/03/14/sunsetting-jazzband _______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3//lists/pypa-committers.python.org Member address: russell@keith-magee.com
+1, makes sense! Thanks, Jacob Coffee Infrastructure Engineer Python Software Foundation ________________________________ From: Russell Keith-Magee <russell@keith-magee.com> Sent: Thursday, March 19, 2026 6:42:56 PM To: Sviatoslav Sydorenko <webknjaz@redhat.com> Cc: PyPA-Committers <pypa-committers@python.org> Subject: [pypa-committers]Re: VOTE: Moving pip-tools to PyPA +1 from me. Yours, Russ Magee %-) On 20 Mar 2026, at 6:50 am, Sviatoslav Sydorenko via PyPA-Committers <pypa-committers@python.org> wrote: Hi PyPA committers, I'd like to open a vote on transferring pip-tools to the PyPA GitHub org: https://github.com/jazzband/pip-tools This is a project that provides a way to generate constraint files and manage virtualenv pins. Sometimes, I call it "an early DIY lock files" implementation. It's used by Dependabot to upgrade requirement/constraint files and is a prior art for what's reimplemented in uv. It's spent most of its life in the Jazzband collaborative maintenance organisation that is getting shut down this year[1]. And so, naturally we're looking for a new home[2]. Since both Stephen and I (webknjaz and sirosen — the current project leads) are already a part of PyPA and it is a tool of the packaging realm, we feel it's a good idea to keep maintaining the project under the familiar umbrella. -- Warm regards, Sviatoslav Sydorenko [1]: https://github.com/jazzband/pip-tools/discussions/2353 [2]: https://jazzband.co/news/2026/03/14/sunsetting-jazzband _______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3//lists/pypa-committers.python.org Member address: russell@keith-magee.com
+1 Thanks for maintaining pip-tools! *Richard Si *(he/him) GitHub: @ichard26 Le jeu. 19 mars 2026, 9 h 39 p.m., Jacob Coffee <jacob.coffee@pyfound.org> a écrit :
+1, makes sense!
Thanks,
Jacob Coffee Infrastructure Engineer Python Software Foundation ------------------------------ *From:* Russell Keith-Magee <russell@keith-magee.com> *Sent:* Thursday, March 19, 2026 6:42:56 PM *To:* Sviatoslav Sydorenko <webknjaz@redhat.com> *Cc:* PyPA-Committers <pypa-committers@python.org> *Subject:* [pypa-committers]Re: VOTE: Moving pip-tools to PyPA
+1 from me.
Yours, Russ Magee %-)
On 20 Mar 2026, at 6:50 am, Sviatoslav Sydorenko via PyPA-Committers < pypa-committers@python.org> wrote:
Hi PyPA committers,
I'd like to open a vote on transferring pip-tools to the PyPA GitHub org:
https://github.com/jazzband/pip-tools
This is a project that provides a way to generate constraint files and manage virtualenv pins. Sometimes, I call it "an early DIY lock files" implementation. It's used by Dependabot to upgrade requirement/constraint files and is a prior art for what's reimplemented in uv.
It's spent most of its life in the Jazzband collaborative maintenance organisation that is getting shut down this year[1]. And so, naturally we're looking for a new home[2]. Since both Stephen and I (webknjaz and sirosen — the current project leads) are already a part of PyPA and it is a tool of the packaging realm, we feel it's a good idea to keep maintaining the project under the familiar umbrella.
-- Warm regards, Sviatoslav Sydorenko
[1]: https://github.com/jazzband/pip-tools/discussions/2353
[2]: https://jazzband.co/news/2026/03/14/sunsetting-jazzband _______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3//lists/pypa-committers.python.org Member address: russell@keith-magee.com
_______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3//lists/pypa-committers.python.org Member address: sichard26@gmail.com
+1 On Thu, 19 Mar 2026, at 22:50, Sviatoslav Sydorenko via PyPA-Committers wrote:
Hi PyPA committers,
I'd like to open a vote on transferring pip-tools to the PyPA GitHub org:
https://github.com/jazzband/pip-tools
This is a project that provides a way to generate constraint files and manage virtualenv pins. Sometimes, I call it "an early DIY lock files" implementation. It's used by Dependabot to upgrade requirement/constraint files and is a prior art for what's reimplemented in uv.
It's spent most of its life in the Jazzband collaborative maintenance organisation that is getting shut down this year[1]. And so, naturally we're looking for a new home[2]. Since both Stephen and I (webknjaz and sirosen — the current project leads) are already a part of PyPA and it is a tool of the packaging realm, we feel it's a good idea to keep maintaining the project under the familiar umbrella.
-- Warm regards, Sviatoslav Sydorenko
[1]: https://github.com/jazzband/pip-tools/discussions/2353
[2]: https://jazzband.co/news/2026/03/14/sunsetting-jazzband _______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3//lists/pypa-committers.python.org Member address: thomas@kluyver.me.uk
+1 On Fri, Mar 20, 2026 at 12:05 Thomas Kluyver <thomas@kluyver.me.uk> wrote:
+1
On Thu, 19 Mar 2026, at 22:50, Sviatoslav Sydorenko via PyPA-Committers wrote:
Hi PyPA committers,
I'd like to open a vote on transferring pip-tools to the PyPA GitHub org:
https://github.com/jazzband/pip-tools
This is a project that provides a way to generate constraint files and manage virtualenv pins. Sometimes, I call it "an early DIY lock files" implementation. It's used by Dependabot to upgrade requirement/constraint files and is a prior art for what's reimplemented in uv.
It's spent most of its life in the Jazzband collaborative maintenance organisation that is getting shut down this year[1]. And so, naturally we're looking for a new home[2]. Since both Stephen and I (webknjaz and sirosen — the current project leads) are already a part of PyPA and it is a tool of the packaging realm, we feel it's a good idea to keep maintaining the project under the familiar umbrella.
-- Warm regards, Sviatoslav Sydorenko
[1]: https://github.com/jazzband/pip-tools/discussions/2353
[2]: https://jazzband.co/news/2026/03/14/sunsetting-jazzband _______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3//lists/pypa-committers.python.org Member address: thomas@kluyver.me.uk
_______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3//lists/pypa-committers.python.org Member address: bussonniermatthias@gmail.com
+1 On Thu, Mar 19, 2026 at 6:50 PM Sviatoslav Sydorenko via PyPA-Committers < pypa-committers@python.org> wrote:
Hi PyPA committers,
I'd like to open a vote on transferring pip-tools to the PyPA GitHub org:
https://github.com/jazzband/pip-tools
This is a project that provides a way to generate constraint files and manage virtualenv pins. Sometimes, I call it "an early DIY lock files" implementation. It's used by Dependabot to upgrade requirement/constraint files and is a prior art for what's reimplemented in uv.
It's spent most of its life in the Jazzband collaborative maintenance organisation that is getting shut down this year[1]. And so, naturally we're looking for a new home[2]. Since both Stephen and I (webknjaz and sirosen — the current project leads) are already a part of PyPA and it is a tool of the packaging realm, we feel it's a good idea to keep maintaining the project under the familiar umbrella.
-- Warm regards, Sviatoslav Sydorenko
[1]: https://github.com/jazzband/pip-tools/discussions/2353
[2]: https://jazzband.co/news/2026/03/14/sunsetting-jazzband _______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3//lists/pypa-committers.python.org Member address: di@python.org
+1 On Fri, Mar 20, 2026, 06:16 Stephen Rosen via PyPA-Committers < pypa-committers@python.org> wrote:
+1
(Of course!) _______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3//lists/pypa-committers.python.org Member address: gaborjbernat@gmail.com
Not a PyPA committer, but I am excited to see pip-tools moving under the PyPA banner. Thanks to Stephen and Sviatoslav for maintaining this lovely tool <3 Seth Larson On Fri, Mar 20, 2026 at 1:16 PM Stephen Rosen via PyPA-Committers < pypa-committers@python.org> wrote:
+1
(Of course!) _______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3//lists/pypa-committers.python.org Member address: seth@python.org
I second it. Henry Sent from my iPhone
On Mar 26, 2026, at 7:16 AM, Sviatoslav Sydorenko via PyPA-Committers <pypa-committers@python.org> wrote:
On Fri, Mar 20, 2026 at 2:02 PM Dustin Ingram <di@python.org> wrote:
+1
I just realized we didn't receive a "seconded" comment in this ML thread that PEP 609 requires. Can somebody fulfill this requirement, please?
-S
_______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3//lists/pypa-committers.python.org Member address: henryfs@princeton.edu
+1
2026年3月20日 06:50,Sviatoslav Sydorenko via PyPA-Committers <pypa-committers@python.org> 写道:
Hi PyPA committers,
I'd like to open a vote on transferring pip-tools to the PyPA GitHub org:
https://github.com/jazzband/pip-tools
This is a project that provides a way to generate constraint files and manage virtualenv pins. Sometimes, I call it "an early DIY lock files" implementation. It's used by Dependabot to upgrade requirement/constraint files and is a prior art for what's reimplemented in uv.
It's spent most of its life in the Jazzband collaborative maintenance organisation that is getting shut down this year[1]. And so, naturally we're looking for a new home[2]. Since both Stephen and I (webknjaz and sirosen — the current project leads) are already a part of PyPA and it is a tool of the packaging realm, we feel it's a good idea to keep maintaining the project under the familiar umbrella.
-- Warm regards, Sviatoslav Sydorenko
[1]: https://github.com/jazzband/pip-tools/discussions/2353
[2]: https://jazzband.co/news/2026/03/14/sunsetting-jazzband _______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3//lists/pypa-committers.python.org Member address: mianghong@gmail.com
+1 Thank you to everyone who maintained pip-tools over the years; as you can imagine, I’m delighted to see this proposal. I should note that Stephen and Sviatoslav are not the only Jazzband project leads per https://jazzband.co/projects/pip-tools and I would recommend extending the offer to join as PyPA members to the others as well, in case it hasn’t happened yet. Jannis
On 19. Mar 2026, at 23:50, Sviatoslav Sydorenko via PyPA-Committers <pypa-committers@python.org> wrote:
Hi PyPA committers,
I'd like to open a vote on transferring pip-tools to the PyPA GitHub org:
https://github.com/jazzband/pip-tools
This is a project that provides a way to generate constraint files and manage virtualenv pins. Sometimes, I call it "an early DIY lock files" implementation. It's used by Dependabot to upgrade requirement/constraint files and is a prior art for what's reimplemented in uv.
It's spent most of its life in the Jazzband collaborative maintenance organisation that is getting shut down this year[1]. And so, naturally we're looking for a new home[2]. Since both Stephen and I (webknjaz and sirosen — the current project leads) are already a part of PyPA and it is a tool of the packaging realm, we feel it's a good idea to keep maintaining the project under the familiar umbrella.
-- Warm regards, Sviatoslav Sydorenko
[1]: https://github.com/jazzband/pip-tools/discussions/2353
[2]: https://jazzband.co/news/2026/03/14/sunsetting-jazzband _______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3//lists/pypa-committers.python.org Member address: jannis.leidel@pyfound.org
If the past maintainers want to continue to be involved, I would welcome them! However, several of them have been inactive for years, and I do not think we can assume that they are aware of the GitHub discussion, this thread, or even of the (graceful) end of Jazzband. I will do my best to reach out to them via several platforms to make sure they are aware, and we can discuss adding them to PyPA if they want to resume their engagement with the project. I think that's the best way to show them the deference and thanks for their hard work that they are owed, but without making the project move to pypa uncertain. We can delay the timeline for the move until we feel comfortable that they have been given an opportunity to respond.
On 23. Mar 2026, at 19:28, Stephen Rosen via PyPA-Committers <pypa-committers@python.org> wrote:
If the past maintainers want to continue to be involved, I would welcome them!
However, several of them have been inactive for years, and I do not think we can assume that they are aware of the GitHub discussion, this thread, or even of the (graceful) end of Jazzband. I will do my best to reach out to them via several platforms to make sure they are aware, and we can discuss adding them to PyPA if they want to resume their engagement with the project.
I think that's the best way to show them the deference and thanks for their hard work that they are owed, but without making the project move to pypa uncertain. We can delay the timeline for the move until we feel comfortable that they have been given an opportunity to respond.
Hold on, putting on my Jazzband hat, it’s not up to a subset of the Jazzband project leads to decide on whether to exclude other existing project leads from a consequential decision like this. For the purpose of Jazzband project leadership, the other project leads were not inactive or emeritus. To be clear, and this will be part of the email I will send to all the remaining Jazzband projects as announced, before PyCon US: the decision to move pip-tools to PyPA has to be unanimous among the project leads for a bulletproof transition between the different governance forms. I now regret that you’ve called for a vote already, but OTOH you also didn’t wait for further instructions as I announced. I have no opinion on whether this vote should be paused until you’ve verified or if you’d like to restart it later in the year. My +1 vote would stand assuming that all project leads have agreed with the move. Jannis
_______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3//lists/pypa-committers.python.org Member address: jannis.leidel@pyfound.org
Obviously our intent wasn't to subvert any process or make extra work, sorry. :( Given that PEP 609 doesn't have any provisions for pausing a vote, I think the best option would be to block the move and start over once we have clarity. This bit of text suffices, regarding additions of projects to pypa: > This proposal must not be opposed by the existing maintainers of the project. Jannis is a maintainer, and I would also support blocking the move if we don't have clarity that it accords with Jazzband requirements. Given that we have four days until the vote closes, I would rather we see if we can sort this out satisfactorily before then. I'll open a jazzband/help issue for us to discuss off of the listhost. I think it's possible that we'll be on good footing to let the vote move forward. On Monday March 23 15:17:09 2026 (-05:00), Jannis Leidel wrote: > > > On 23. Mar 2026, at 19:28, Stephen Rosen via PyPA-Committers wrote: > > > > If the past maintainers want to continue to be involved, I would welcome them! > > > > However, several of them have been inactive for years, and I do not think we can assume that they are aware of the GitHub discussion, this thread, or even of the (graceful) end of Jazzband. > > I will do my best to reach out to them via several platforms to make sure they are aware, and we can discuss adding them to PyPA if they want to resume their engagement with the project. > > > > I think that's the best way to show them the deference and thanks for their hard work that they are owed, but without making the project move to pypa uncertain. We can delay the timeline for the move until we feel comfortable that they have been given an opportunity to respond. > > Hold on, putting on my Jazzband hat, it’s not up to a subset of the Jazzband project leads to decide on whether to exclude other existing project leads from a consequential decision like this. For the purpose of Jazzband project leadership, the other project leads were not inactive or emeritus. > > To be clear, and this will be part of the email I will send to all the remaining Jazzband projects as announced, before PyCon US: the decision to move pip-tools to PyPA has to be unanimous among the project leads for a bulletproof transition between the different governance forms. I now regret that you’ve called for a vote already, but OTOH you also didn’t wait for further instructions as I announced. > > I have no opinion on whether this vote should be paused until you’ve verified or if you’d like to restart it later in the year. > > My +1 vote would stand assuming that all project leads have agreed with the move. > > Jannis > > > _______________________________________________ > > PyPA-Committers mailing list -- pypa-committers@python.org > > To unsubscribe send an email to pypa-committers-leave@python.org > > https://mail.python.org/mailman3//lists/pypa-committers.python.org > > Member address: jannis.leidel@pyfound.org > >
My mail client seems to have eaten all of the line endings when I tried to reply... Sorry to anyone trying to read that. I've included a cleaned up version as part of a Jazzband issue here, so that we can discuss off-list: https://github.com/jazzband/help/issues/427
I'm very pleased to share that we've just heard back from the last of the pip-tools maintainers, in support of the move! Two of our maintainers would like to be removed from the project (davidovich and vphilippon). Albert Tugushev (atugushev) would like to join us in the move to PyPA, so when we do the move I believe he will need to be added to the pypa GitHub org and this mailing list. Cheers, -Stephen P.S. Yes, I *was* low-key stressed about this. I'm glad we got such a nice resolution.
Something that's worth noting here, unless something has changed, is that inviting a user to become a member of the GitHub organization consumes a paid seat whereas adding a user to a public repository as a collaborator does not. I remember a discussion about the cost a few years ago. On Mon, Mar 23, 2026 at 2:28 PM Stephen Rosen via PyPA-Committers < pypa-committers@python.org> wrote:
If the past maintainers want to continue to be involved, I would welcome them!
However, several of them have been inactive for years, and I do not think we can assume that they are aware of the GitHub discussion, this thread, or even of the (graceful) end of Jazzband. I will do my best to reach out to them via several platforms to make sure they are aware, and we can discuss adding them to PyPA if they want to resume their engagement with the project.
I think that's the best way to show them the deference and thanks for their hard work that they are owed, but without making the project move to pypa uncertain. We can delay the timeline for the move until we feel comfortable that they have been given an opportunity to respond. _______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3//lists/pypa-committers.python.org Member address: ofekmeister@gmail.com
+1 on PyPA as a destination (I would have suggested it if you didn't). I think the two votes are separate, though. The PyPA one is about accepting the move, while the pip-tools side is getting consensus amongst the existing leads that PyPA makes sense as a new home. In principle approval from PyPA doesn't represent a *commitment* to move. Cheers, Alyssa. -- Alyssa Coghlan | Brisbane, Australia On Fri, 20 Mar 2026, 8:50 am Sviatoslav Sydorenko via PyPA-Committers, < pypa-committers@python.org> wrote:
Hi PyPA committers,
I'd like to open a vote on transferring pip-tools to the PyPA GitHub org:
https://github.com/jazzband/pip-tools
This is a project that provides a way to generate constraint files and manage virtualenv pins. Sometimes, I call it "an early DIY lock files" implementation. It's used by Dependabot to upgrade requirement/constraint files and is a prior art for what's reimplemented in uv.
It's spent most of its life in the Jazzband collaborative maintenance organisation that is getting shut down this year[1]. And so, naturally we're looking for a new home[2]. Since both Stephen and I (webknjaz and sirosen — the current project leads) are already a part of PyPA and it is a tool of the packaging realm, we feel it's a good idea to keep maintaining the project under the familiar umbrella.
-- Warm regards, Sviatoslav Sydorenko
[1]: https://github.com/jazzband/pip-tools/discussions/2353
[2]: https://jazzband.co/news/2026/03/14/sunsetting-jazzband _______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3//lists/pypa-committers.python.org Member address: ncoghlan@gmail.com
On Thu, Mar 19, 2026 at 11:50 PM Sviatoslav Sydorenko <webknjaz@redhat.com> wrote:
I'd like to open a vote on transferring pip-tools to the PyPA GitHub org:
So a week has passed since Henry seconded the proposal and 14 committers have responded with "+1" earlier, with no unresolved objections recorded. Meaning, we can officially declare that the vote is over and the proposal has passed. Stephen and I will coordinate the transfer off-list, in the discussion over in the pip-tools repository. Thanks everyone! - Sviatoslav
participants (19)
-
Alyssa Coghlan -
Bernat Gabor -
Carol Willing -
Dustin Ingram -
Frost Ming -
Henry F. Schreiner -
Jacob Coffee -
Jannis Leidel -
Matthias Bussonnier -
Mike -
Nate Prewitt -
Ofek Lev -
Paul Moore -
Richard Si -
Russell Keith-Magee -
Seth Larson -
Stephen Rosen -
Sviatoslav Sydorenko -
Thomas Kluyver