Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maintainers needed #176

Open
bosd opened this issue Jul 15, 2023 · 16 comments
Open

Maintainers needed #176

bosd opened this issue Jul 15, 2023 · 16 comments

Comments

@bosd
Copy link

bosd commented Jul 15, 2023

It seems like excalibur is dead:

  • 7 sept 20202
  • Last PyPI release: 2020-03-21 - @vinayak-mehta is the only owner
  • Several PRs which look ready to be merged, but are still open
  • Current release seems to be broken on modern systems. (win 10 refresh issue)

Only 10 contributors on the project.
New contributors are unable to open a PR.

Please update repo settings so others can open PR's.
Now there is an error:
Pull request creation failed. Validation failed: must be a collaborator

@MartinThoma , @vinayak-mehta

@foarsitter
Copy link
Contributor

In my opinion we can best proceed in the same way with excalibur as with camelot.

-> Create an empty project with https://github.com/cjolowicz/cookiecutter-hypermodern-python
-> Merge code into new template
-> Make tests succeed
-> Run black + isort
-> Merge

@bosd
Copy link
Author

bosd commented Jul 15, 2023

Didn't know cookie cutter. Looks impressive.
Can you move forward with that?

@bosd
Copy link
Author

bosd commented Jul 15, 2023

@dimitern & @vinayak-mehta Could you please edit the repo settings so PR's can be opened. 🙏

@vinayak-mehta Could you please add more maintainers to Pypi.
You can add me, @foarsitter and possible give acces to a bot from the cookiecutter project, once that is setup.

@MartinThoma
Copy link
Contributor

@foarsitter @bosd It seems to me that you care most about Excalibur / Camelot. Would you mind to give me your e-mail address (mine is [email protected]; you can just ping me via e-mail).

I have some ideas which I would like to discuss in private first.

@marcozzxx810
Copy link

Hi @MartinThoma, I also like to contribute more to camelot and Excalibur. Do you think you can loop me into the discussion?

my email: [email protected]

@MartinThoma
Copy link
Contributor

MartinThoma commented Aug 25, 2023

@vinayak-mehta I do have the permission to merge (thank you :pray), but

  1. No permission on PyPI. I cannot release
  2. Not enough permissions on GitHub. I cannot change project settings (like the issue mentioned here or adding repository secrets for a release action) - same goes for camelot.

@marcozzxx810
Copy link

Except the release problem, what is the next step? Seem no one is maintaining issue, PR, milestones.

@MartinThoma
Copy link
Contributor

@marcozzxx810 I'm currently writing to Vinayak to see if we can merge the camelot-dev organization into the py-pdf organization. This is why I wanted the e-mails of @bosd and @foarsitter as it might be easier to exchange thoughts in that private round than here publicly. Besides that, I would keep all discussions public.

I'm sorry to say this, but I think you have to be patient. I guess nothing will happen in the next two weeks. What will happen afterwards depends on Vinayaks opionion of moving camelot-dev into py-pdf or not. If we move, I'm very confident that the camelot community can make pretty rapid progress. I would mainly help with setting up CI / ensuring the handling of issues / PRs / releases works smoothly (likely not actual development).

@marcozzxx810
Copy link

Hi @MartinThoma, understood!

Sorry for being inpatient, just wish to know more about situations and have more visibility. Since there is no information/update in camelot repo.

Really appreciate your effort in communication. Keep us posted about the situation

@marcozzxx810
Copy link

For the two repo problems, have we reach out to the point of contact?

I guess we still need to settle that regardless of the migration happen or not.

@MartinThoma
Copy link
Contributor

I am writing e-mails to @vinayak-mehta :-)

@marcozzxx810
Copy link

@MartinThoma any news/update?

@MartinThoma
Copy link
Contributor

MartinThoma commented Sep 24, 2023

Sadly not.

To be honest, I'm pretty frustrated. I have enough permissions to feel responsible for the project, but not enough to actually improve it.

@vinayak-mehta If I don't have the full Github and PyPI permissions until 1st of November 2023, I'll give the permissions back and remove myself from the project.

@foarsitter
Copy link
Contributor

Feeling the same as @MartinThoma, it should be fun but keep running into limitations isn't.

@evan54
Copy link

evan54 commented Mar 12, 2024

did this ever get resolved - is there a similar style replacement package that people can use?

@bosd
Copy link
Author

bosd commented Mar 12, 2024

ever get resolved - is there a similar style replacement package that people can use?

Sadly no, But we moved on and merged it into py-pdf organization.
The new home is here: https://github.com/py-pdf/pypdf_table_extraction

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants