-
-
Notifications
You must be signed in to change notification settings - Fork 234
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
Comments
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 |
Didn't know cookie cutter. Looks impressive. |
@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. |
@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. |
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] |
@vinayak-mehta I do have the permission to merge (thank you :pray), but
|
Except the release problem, what is the next step? Seem no one is maintaining issue, PR, milestones. |
@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). |
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 |
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. |
I am writing e-mails to @vinayak-mehta :-) |
@MartinThoma any news/update? |
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. |
Feeling the same as @MartinThoma, it should be fun but keep running into limitations isn't. |
did this 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. |
It seems like excalibur is dead:
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
The text was updated successfully, but these errors were encountered: