We need a new maintainer

[arsenovic]

@eric-wieser @hugohadfield @rkern

hi guys, i have noticed that we need a new maintainer on this project.

its a great tool and would be a shame to let it wither away and get forked.

any thoughts on how to go about this? maybe we could do a sprint dev cycle to clean it up for an easier hand-off? possibly simplify the maintenance as much as possible?

[zevisert]

Hey team, I'm new here - and definitely wouldn't be in a position to help maintain. I just found this library today, and it's probably exactly what I need. As a new user, I just installed from pypi and immediately ran into #431/#439 - I know I can downgrade numba, but since it's fixed but not tagged there's no release. Publishing 1.5.0 tag would be greatly appreciated :)

[arsenovic]

hi @zevisert ! great to hear. perhaps you could try to make a new release in a PR?

@eric-wieser are there instructions for making a release anywhere?

[zevisert]

I'll take a look at drafting something tonight, sure. Aside from release notes or updated documentation, it looks like the GitHub actions workflow are already configured to publish when a git tag is pushed

[zevisert]

@arsenovic take a look at #442, I outlined what I think needs to be done based on what seems to have been done for previous releases

[hugohadfield]

Apologies for not being involved with things recently, I think a lot of the pain points around keeping clifford maintained are due to the pretty tight integration with numba (my bad). My personal push for things that should be done to minimise maintenance burden:

1. Make numba a totally optional import
2. Remove the h5py dependency (I dont think anyone uses the saving multivectors system anyway)
   At that point we should have a much more future proofed library