pearu/pylibtiff

Looking for maintainers?

djhoese opened this issue · 7 comments

@pearu What's your availability for this project? It looks like I still have some minimal permissions based on my old participation in the project, but I'm wondering if you're open to more maintainers or increasing my level of permissions to fix some of the "modernization" issues (#134, #133, etc). I also have some others in the Pytroll community (maintainers of satpy, pyresample) who use this library and would be willing to help review things when they can.

What are your thoughts?

If anyone else is willing to help maintain this library feel free to comment.

Edit: Looks like I have permission to merge pull requests so I guess I don't need to ask, but I'm not familiar with the current release process and want to respect any current practices of the project.

pearu commented

My availability for pylibtiff includes reviewing/merging PRs, not so much for solving particular issues.
Feel free to ping me in issues/PRs if feedback/reviews/landing is needed.

I am fine if contributors merge PRs with the requirement that somebody else (other contributors, me, etc) will sanity-check/approve the PRs.

Great! Would it be possible (if you're comfortable) to give me higher permissions on this github repository? Maybe to at least add another contributor. Otherwise if you have any info on the history of the bundled bitarray I'd like to hear it to understand some of the issues we've discovered with Python 3.11.

...and also, do you pay for Travis-CI? Or are you looking to migrate to something that is (currently) free like GitHub Actions?

...and supporting Python 2.7? Ok with dropping that?

@djhoese Glad to see someone else has realized libtiff is broke with 3.11. I'd love to get this updated asap because I use it for a personal project and don't want to downgrade everything to 3.10 just for this. I use numpy extensively so can probably help with the modernization of numpy usage. Flipside is, don't know anything about the C libraries and don't know how I would test without some quick fix for the bitarray problem. Please let me know if I can be useful.

@gcbrown Let's move the 3.11 discussion to #133

Version 0.5.0 is now available on PyPI. I'm waiting for the conda-forge bot to pick it up where I'll then work on getting the Python 3.11 build working on conda-forge. Closing this as maintenance is now much easier for this package and someone besides @pearu released a package 😉