Maintenance of CharPyLS?

[mrbean-bremen]

First, I want to thank you for the work in this repo - we (at pydicom) very much appreciate it, and we have been using this it in pydicom for decoding JPEG-LS images for years (and would like to continue to do so).

I made a simple PR for Python 3.11 compatibility yesterday, and afterwards noted that there there hasn't been any activity in this repo for years, so under the assumption that the repo is not maintained anymore, I created a fork that has the PR integrated, and which we will use at least temporary.

If this repo is still maintained, and the PR(s) will be reviewed and eventually merged, we can remove that repo again. That would be the preferred option in my view.

Otherwise, there are a few options:

• the maintainer invites collaborators who are able to handle maintance in the future
• this repo is officially transferred to pydicom (in this case the other one will be removed), or another suitable organization, where more maintainers can be added
• this repo is archived and points to our fork for further development, possibly giving us also the possibility to publish new PyPi versions (by adding more maintainers in PyPi)

Of these options, I personally would prefer the transfer to pydicom, as it would avoid having a fork.

Last, if we get no response here, we will proceed with our fork and add a PyPi package of our own with a new name.

Thank you!

[mrbean-bremen]

Update:
We have now published a PyPi package from our fork pydicom/pyjpegls, which contains wheels for several Python versions and systems. We will go ahead to maintain that fork.