On 9/19/25 6:17 AM, Thomas Goirand wrote:
On 9/18/25 12:21 PM, Takashi Kajinami wrote:
Yes I already prepared https://review.opendev.org/c/openstack/yaql/ +/961398 , but would be nice if I can ask someone else to review it.
In what way that's better than taking over the lib itself, and maintaining it?
If you read the README in the ply repository, you may find that the author is willing to keep the repository under his control while he intentionally stopped new release to avoid himself from being part of "your supply chain" so it does not sound feasible to take over the repo.
Vendoring is bad... The fact that upstream for ply says we should do that doesn't change the fact.
It may sound bad to you but that's what the author suggests. I'd avoid forking the project because we are only interested in our own usage within yaql. Given how widely yaql may be used I'm unsure if we can maintain it as a full fork project, unless someone actually steps up here to maintain the full fork.
Cheers,
Thomas Goirand (zigo)