Given that vmdpy is now maintained in sktime (official fork/continuation), we should transfer any open issues to the sktime issue tracker and handle them there.
@vrcarva, for the transfer: How about June 14, 14 UTC, or June 17, anytime 11-12, or 14?
It is maybe easier to send direct messages on the sktime discord: https://discord.com/invite/54ACzaFsn7
fkiraly
commented
4 months ago
Given that
vmdpyis now maintained insktime(official fork/continuation), we should transfer any open issues to thesktimeissue tracker and handle them there.Continuing the discussion from https://github.com/vrcarva/vmdpy/pull/19#issuecomment-2150647590 here, since I'm apprehensive of messages on closed PRs not causing a notification.
@vrcarva, for the transfer: How about June 14, 14 UTC, or June 17, anytime 11-12, or 14? It is maybe easier to send direct messages on the sktime discord: https://discord.com/invite/54ACzaFsn7