Replies: 7 comments 10 replies
-
I don't know enough about the history of Pants and Pex to know why there's friction here. To me it seems like if you don't want to develop Pex under the Pantsbuild banner, noone can stop you from doing it elsewhere. I haven't gotten the impression that Pantsbuild as an organization gets very involved in the development of pex, or puts lots of requirements on how it's ran. Either way, pex seems to me like such an integral part of pants at this point that it cannot be easily replaced in the short term. I realize this dependence probably adds to your work, and being part of the organization puts you in the blast zone via association. Still, even if we part ways Pantsbuild is going to expose a lot of people to pex, and issues will be filed in relation to that. Maybe there'll be less pressure on you to solve them, fewer pings, and maybe we'll be more inclined to solve them from the pants end. However, I've also felt that pex is yours and onboarding others isn't in your interest, nor that I could contribute accordingly. So no matter the "physical" location of the project, I'm more interested in what we can do to cooperate better, if that's the issue. Maybe moving pex is enough, but if there's other concerns I think those are worth addressing separately, here or elsewhere. But as said, I'm still "new" (and thus maybe a demanding user ;-)) |
Beta Was this translation helpful? Give feedback.
-
I'm generally of the opinion that whoever puts in the legwork gets to make the decisions. This is partly out of courtesy, but mostly because the person doing the work has the best perspective on those decisions. So as the ~sole maintainer, if this makes sense to you, I support it. I would greatly prefer transferring the project to another org to forking. Pants already consumes Pex as a third-party binary, and Pex is highly scrupulous about maintaining backwards compatibility, so this doesn't impose much hardship on Pants that I can see. As you mention, we already work this way with scie, so I hardly think this is an outlandish state to be in... I believe that Pants is the major (although not exclusive) consumer of Pex? So most bug reports, feature requests, contributions, code reviews and so on will, I would guess, tend to still involve people in the Pants community. Those folks (myself included) will now have to operate under a different set of guidelines. Which is totally fine, and we'll all get used to it pretty quickly, but in the short term there will probably be some confusion, misunderstandings or friction. So let's make sure we resolve those with as little tension as possible until we settle in to the new normal. |
Beta Was this translation helpful? Give feedback.
-
Ok, this is done and the repo is now housed at https://github.com/pex-tool/pex. There will be some follow-up activity over the next few days to cleanup docs, etc. Thanks everyone. |
Beta Was this translation helpful? Give feedback.
-
@hrfuller, @Eric-Arellano and @stuhood: Pex has moved here to https://github.com/pex-tool/pex. I'm beginning a clean up process and part of that is auditing PyPI access / making sure publishing still works etc. You three are maintainers on PyPI, but not active maintainers in reality. My inclination is to trim you all off that list. I'll proceed to do so later next week unless I hear objections. |
Beta Was this translation helpful? Give feedback.
-
Ok, and as part of my 1st pass audit, pantsbuild/pants has no references to pantsbuild/pip - this is just used for the home of Pex's vendored / patched Pip 20.3.4. I'll transfer that repo to the pex-tool org as well. |
Beta Was this translation helpful? Give feedback.
-
And https://github.com/pantsbuild/setuptools is likewise just used by Pex for a vendored setuptools patch. I'll move that as well. |
Beta Was this translation helpful? Give feedback.
-
Thanks folks. As of v2.2.1 I consider the project fully migrated and a bit improved with the new doc site and embedded docs. |
Beta Was this translation helpful? Give feedback.
-
This is driven by me being the ~sole maintainer and having a harder and harder time dealing with Pantsbuild contributions and interactions charitably. Pantsbuild should not have to suffer my quirks in particular and Pex has no real tie to Pants or Pantsbuild except via history.
Concretely, I'd like to:
I can see two paths forward that meet these goals:
Either of these options requires Pantsbuild org buy in; so I'm looking for your feedback.
I'll seed this with a few mentions of folks who can pull in others if they wish @benjyw, @stuhood, @kaos, @huonw, @tgolsson and @thejcannon.
Beta Was this translation helpful? Give feedback.
All reactions