We need more maintainers

[MartinThoma]

It seems like camelot is dead:

• Last commit: 2021-07-11 - @dimitern is the only other project owner besides @vinayak-mehta
• Last PyPI release: 2021-07-11 - @vinayak-mehta is the only owner
• Several PRs which look ready to be merged, but are still open

Besides the owner there are only 35 other contributors.

https://opencollective.com/camelot might be another way to check if it's dead.

Does anybody know more? Should we try to transfer the project to https://github.com/jazzband ?

[MartinThoma]

Or is somebody there who would like to become a maintainer?

[vinayak-mehta]

Hi @MartinThoma, sorry for not being responsive here. I've been busy with some life stuff for some time now and haven't had the mindspace to look into the issues here. I've been wanting to get back into it, I'll look into them over this weekend.

I also want to stop being a single point of failure here and would love to get help maintaining camelot going forward.

[foarsitter]

Is there any movement on this topic?

[ramSeraph]

@vinayak-mehta Would you mind if I post this on the Indian FOSS and opendata channels? This tool has been extremely helpful in dealing with the PDF crap Indian Government puts out.

[foarsitter]

Sorry for my inpatientence but the show must go on. In order to take camelot to production I created a fork and released it to pypi under camelot-fork==0.20.0. My intentions are limited and I hope this project finds new maintainers soon.

When the request came to extract tables from pdf files I thought it would be very tricky job but camelot does it all. Therefore I want to express my gratitude to all of you that made that possible.

If people are in need of a fix I'm willing to accept pull request as long as they have test-coverage.

[vinayak-mehta]

Sorry for being a bit unresponsive since I created this issue. I've pushed a release based on @MartinThoma's last PR: https://pypi.org/project/camelot-py/

@MartinThoma Thank you for the PR, would you like to be added to the github org so that you have push access to the repo?

@foarsitter Are you interested in maintaining the project here instead of the fork? I can add you to the github org too.

[MartinThoma]

Thank you for making a new release 🙏

would you like to be added to the github org so that you have push access to the repo?

I would probably not be super active as I spend most of my time with pypdf. If that is ok for you, then yes, please add me :-) I could probably go over a couple of the PRs / introduce update CI so that maintaining the library becomes easier :-)

[vinayak-mehta]

@MartinThoma That would be awesome! Just sent you an invite ✉️

[foarsitter]

@vinayak-mehta should be awesome

[MartinThoma]

Are there any rules I should follow, e.g.

1. Reviews: When I make a PR, should I ask you (or somebody else) for a review before merging it? (Here is the first one, btw: MAINT: Drop Python 3.6 from CI + skip failing Mac tests #356 😄 )
2. Commit Messages: e.g. something like https://docs.scipy.org/doc/scipy/dev/contributor/development_workflow.html#writing-the-commit-message ?
3. Merges: Merge / Squash+Merge / Rebase+Merge: I prefer squash+merge, but you seem to do normal merges only. Is sqash+merge ok?
4. Tests: Do you have any hard rules in regards to unit tests, e.g. that every new feature needs to have full test coverage?