You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@zsteve and @devmotion, I see that some PRs are not being addressed and I saw some a complaint on Slack about compat downgrades. I'm guessing you guys must be swamped with other priorities (much like me), and maintaining this package has probably fallen off the radar.
I was wondering if we should try to "pass the torch" somehow to people more focused on Optimal Transport, and that could keep on maintaining it and implementing new features.
The text was updated successfully, but these errors were encountered:
Hi Davi,Yes unfortunately I've been swamped with my PhD these days. I agree that it would be great if others may be interested to maintain and continue developing the package.
Do let me know if you know of anyone who may be interested. I'll also try and see about this.
Stephen
On Sat, 04/01/2025 02:08, Davi Sales Barreira ***@***.***> wrote:
@zsteve and @devmotion, I see that some PRs are not being addressed and I saw some a complaint on Slack about compat downgrades. I'm guessing you guys must be swamped with other priorities (much like me), and maintaining this package has probably fallen off the radar.
I was wondering if we should try to "pass the torch" somehow to people more focused on Optimal Transport, and that could keep on maintaining it and implementing new features.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
@zsteve and @devmotion, I see that some PRs are not being addressed and I saw some a complaint on Slack about compat downgrades. I'm guessing you guys must be swamped with other priorities (much like me), and maintaining this package has probably fallen off the radar.
I was wondering if we should try to "pass the torch" somehow to people more focused on Optimal Transport, and that could keep on maintaining it and implementing new features.
The text was updated successfully, but these errors were encountered: